logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-01-07 16:43:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

improve peer and connection managment section

Browse Source
This commit is contained in:
Sasha 2024-07-02 12:22:01 +02:00
parent 988a022c36
commit 9eb63db372
No known key found for this signature in database
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
informational/req-res-reliability.md
View File

@ -46,9 +46,11 @@ To address this we suggest following metrics:
In case a protocol failed to use any service node more than once - In case a protocol failed to use any service node more than once -
connection to it should be dropped and a new service node should be connected and added to the pool instead. connection to it should be dropped and a new service node should be connected and added to the pool instead.
- During discovery of new peers it is better to filter out based on ENR / multiaddress. For example in some cases `circuit-relay` addresses are not needed when we try to find and connect to peers directly. - During discovery of new service nodes it is better to filter out based on ENR / multiaddress.
For example in some cases `circuit-relay` addresses are not needed when we try to find and connect to service nodes directly.
- When peer is discovered second time, we need to be sure to keep connection information up to date in Peer Store. - When a service node is discovered second time,
we need to be sure to keep connection information up to date in Peer Store.
### Light Push ### Light Push