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

*the* two *minute* cache interval; similar -> similarly

Browse Source
This commit is contained in:
James Ray
2018-08-30 16:34:54 +10:00
committed by GitHub
parent 268cd55088
commit ce69d5aac8
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
pubsub/gossipsub/README.md
View File

@@ -226,7 +226,7 @@ The `seen` cache is the flow control mechanism. It tracks
the message IDs of seen messages for the last two minutes. It is
separate from `mcache` for implementation reasons in Go (the `seen`
cache is inherited from the pubsub framework), but they could be the
same data structure. Note that two minutes cache interval is non-normative;
same data structure. Note that the two minute cache interval is non-normative;
a router could use a different value, chosen to approximate the propagation
delay in the overlay with some healthy margin.
@@ -275,7 +275,7 @@ After processing the payload, it then processes the control messages in the enve
requesting peer.
When the router publishes a message that originates from the router itself (at the
application layer), then it proceeds similar to the payload reaction:
application layer), then it proceeds similarly to the payload reaction:
- It forwards the message to every peer in `peers.floodsub[topic]`.
- If it is subscribed to the topic, then it must have a set of peers in `mesh[topic]`,
to which the message is forwarded.