AtHeartEngineer/specs
1
0
Fork 0
mirror of https://github.com/vacp2p/specs.git synced 2026-01-08 23:08:09 -05:00
Code Issues Packages Projects Releases Wiki Activity

pubsub/: Clarify stream management (#442)

Browse Source
This commit is contained in:
Cayman
2022-09-03 21:20:04 -04:00
committed by GitHub
parent a6c52ba13e
commit 187b5d60c9
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
pubsub/README.md
View File

@@ -75,6 +75,13 @@ You can find information about the PubSub research and notes in the following re
- [gossipsub](https://github.com/libp2p/specs/tree/master/pubsub/gossipsub#implementation-status) - [gossipsub](https://github.com/libp2p/specs/tree/master/pubsub/gossipsub#implementation-status)
- [EpiSub](https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/episub.md), an epidemic broadcast tree router (defined 2018, not yet started as of Oct 2018) - [EpiSub](https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/episub.md), an epidemic broadcast tree router (defined 2018, not yet started as of Oct 2018)
## Stream management
Data should be exchanged between peers using two separately negotiated streams,
one inbound, one outbound. These streams are treated as unidirectional streams.
The outbound stream is used only to write data. The inbound stream is used only
to read data.
## The RPC ## The RPC
All communication between peers happens in the form of exchanging protobuf RPC All communication between peers happens in the form of exchanging protobuf RPC