Listen multiple channels on one connection
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8.7k
- Forks
- 374
- Avg merge
- 11d 16h
- Merged PRs (30d)
- 1
Description
If listening for multiple channels, it is wasteful to use a separate connection for each one.
I understand this is related to the choice to reuse listeners for a single channel.
While there is advantages to that in some case, in other cases (many channels), it is advantageous to reuse a connection for multiple channels.
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
No file, test, or entry point is named. Start by tracing how listeners and connections are created and reused for multiple channels, then determine the API and lifecycle behavior needed for sharing one connection. Done means multiple channels can be listened to through one connection without breaking existing single-channel behavior, with coverage for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs, postgresql
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100