Pubsub: Specify how streams should be handled
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.8k
- Forks
- 320
- Avg merge
- 11d 15h
- Merged PRs (30d)
- 1
Description
Currently go-libp2p uses long-lived streams, whereas rust-libp2p initializes a new stream per message. These implementations are currently incompatible.
This issue is to add specification of how streams should be handled in pubsub/gossipsub.
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 pubsub/gossipsub and contrasts long-lived streams in go-libp2p with per-message streams in rust-libp2p, but it names no files or tests. Begin by reviewing both implementations and their current stream behavior, then document a compatible stream-handling specification for pubsub/gossipsub.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, rust
- Domain
- distributed-systems, networking
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100