-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update peer selection options for light protocols #787
Conversation
@richard-ramos , it is becoming challenging to maintain both peerManager and option of using waku protocols without peer-manager (i.e using utils peer code). As you can see in this PR, there already is a lot of checks and duplicate code generated. Now with peer-selection based on pubSubTopic, which cannot be done by default libp2p peerStore alone(since we store peer specific pubSub topics in wakuPeerStore), I am wondering if it is time to retire this option of peerutils without peerManager. WDYT? |
Jenkins BuildsClick to see older builds (84)
|
As long as the scenarios covered by the utils function can be met with the peer manager, it should be okay to retire the functions:
|
The scenarios would be covered in peerManager. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good.
Left some few comments/questions
…dPeer is already specified
Co-authored-by: richΛrd <[email protected]>
Description
Update req/resp protocols to use new peerSelection logic based on pubSub/contentTopic as per #680
Changes
Tests