-
Notifications
You must be signed in to change notification settings - Fork 58
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
chore: refactor filter to react when the remote peer closes the stream #3281
Conversation
Better control when the remote peer closes the WakuFilterPushCodec stream remotely. For example, go-waku closes the stream for every received message. On the other hand, js-waku keeps the stream opened. Therefore, we support both scenarios.
e3cf52a
to
9d004e4
Compare
You can find the image built from this PR at
Built from aa2632a |
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.
LGTM, thanks so much!
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.
Awesome! Thank you.
I think it is all good however one time getStreamByPeerIdAndProtocol
would be better placed at libp2p switch and dialer level, imho.
Good point! Something to consider in the future if other projects may benefit from that as well: @richard-ramos |
#3281) Better control when the remote peer closes the WakuFilterPushCodec stream. For example, go-waku closes the stream for every received message. On the other hand, js-waku keeps the stream opened. Therefore, we support both scenarios.
Description
Better control when the remote peer closes the WakuFilterPushCodec stream remotely.
For example, go-waku closes the stream for every received message. On the other hand, js-waku keeps the stream opened. Therefore, we support both scenarios.
Issue
closes #3271