libp2p / libp2p/go-libp2p-pubsub
Allow prioritization of traffic per topic
Open
Nobody has claimed this yet.
req:filecoin
- Dominant language
- Go
- Stars
- 364
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
I'd like to be able to prioritize traffic on one topic over traffic from another, so that messages from topic B would never cause delays (as much as is practical) for topic A, if topic A hash higher priority.
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
The issue names no files, tests, or entry points. Start by locating how topic traffic is scheduled and identify where topic priority could be applied. Done should mean higher-priority topic A traffic does not experience avoidable delays caused by lower-priority topic B traffic, with tests defining that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100