Optimise subscription model
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 489
- Forks
- 293
- Avg merge
- 18h 35m
- Merged PRs (30d)
- 3
Description
It should be possible to reuse a global event / block subscription between calls to reduce load on the underlying websocket connection.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how global event and block subscriptions are created and how calls establish or reuse the underlying websocket connection. Identify the subscription lifecycle and its existing tests, then define how reuse should work without breaking cleanup or concurrent calls. Done means repeated calls can share one subscription and websocket connection, with tests covering reuse and teardown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100