mirror of https://github.com/vacp2p/rfc.git
Update content/docs/rfcs/34/README.md
Co-authored-by: Hanno Cornelius <68783915+jm-clius@users.noreply.github.com>
This commit is contained in:
parent
f38e6836c7
commit
2813e1dc7c
|
@ -49,7 +49,8 @@ To get the best anonymity properties with respect to response peer sets, respond
|
||||||
|
|
||||||
To save bandwidth, and as a trade off to anonymity,
|
To save bandwidth, and as a trade off to anonymity,
|
||||||
responders MAY maintain a larger cache of exchange peers and randomly sample response sets from this local cache.
|
responders MAY maintain a larger cache of exchange peers and randomly sample response sets from this local cache.
|
||||||
This local cache SHOULD store peers by `cluster_id`/`shard` for faster retrieval. For peers without shard info, cache can maintain another list of peers.
|
This local cache SHOULD store peers by `cluster_id`/`shard` for faster retrieval.
|
||||||
|
For peers without shard info, the cache can maintain a separate set of peers.
|
||||||
The size of each `cluster_id`/`shard` pair being maintained in cache SHOULD be large enough to allow randomly sampling peer sets that (on average) do not overlap too much.
|
The size of each `cluster_id`/`shard` pair being maintained in cache SHOULD be large enough to allow randomly sampling peer sets that (on average) do not overlap too much.
|
||||||
The responder SHOULD periodically replace the oldest peers in the cache.
|
The responder SHOULD periodically replace the oldest peers in the cache.
|
||||||
This document provides recommended choices for the cache size in the [Implementation Suggestions Section](#implementation-suggestions).
|
This document provides recommended choices for the cache size in the [Implementation Suggestions Section](#implementation-suggestions).
|
||||||
|
|
Loading…
Reference in New Issue