d389d96789
Hello! This PR aim to refactor rendezvous code so that it is easier to impl. Waku rdv strategy. The hardcoded min and max TTL were out of range with what we needed and specifying which peers to interact with is also needed since Waku deals with peers on multiple separate shards. I tried to keep the changes to a minimum, specifically I did not change the name of any public procs which result in less than descriptive names in some cases. I also wanted to return results instead of raising exceptions but didn't. Would it be acceptable to do so? Please advise on best practices, thank you. --------- Co-authored-by: Ludovic Chenut <ludovic@status.im> |
||
|---|---|---|
| .. | ||
| connectivity | ||
| perf | ||
| pubsub | ||
| secure | ||
| identify.nim | ||
| ping.nim | ||
| protocol.nim | ||
| pubsub.nim | ||
| rendezvous.nim | ||