-
Notifications
You must be signed in to change notification settings - Fork 0
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
transports/webrtc: Implement message framing #10
transports/webrtc: Implement message framing #10
Conversation
…brtc-message-framing
With mxinden/specs@865f4f2 the RESET no longer resets both write and read part of a stream, but only the former.
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.
looks good so far 👍
Writing the muxer test suite turns out to be a bit more complex than I thought it would. I'll see to dedicate most of tomorrow to that. Might have to first write tests specific to this impl. |
Looks like the branch has diverged from anton/webrtc-transport. @thomaseizinger do you mind fixing this? |
Yep, I should have time for this tomorrow! I got caught up trying to implement stream-resets properly on the other muxers so we can have a standardised test suite but that turns out to be a bigger effort. |
…brtc-message-framing
Logging these state transitions is no longer really worth it because we have changed the design to have many more functions which would all require logging now.
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.
I also implemented sending of reset flags now for dropped substreams. I think this is now actually complete :) |
@mxinden Can you review this please? |
@mxinden I think you still should be able to review here or in main PR (whatever you prefer). |
Updates #2759 See melekes/rust-libp2p#10 and libp2p/specs#412 (comment) Co-authored-by: Pierre Krieger <[email protected]>
I will review the main branch. Sorry for being a bottleneck here. Thanks @thomaseizinger for driving this all the way from the spec to the implementation! 🙏 |
Description
This continues on #9 which I unfortunately couldn't push to. This PR is based off a branch in
rust-libp2p
now so @mxinden should definitely have push access and because it targets @melekes's PR he should have push access to :)Links to any relevant issues
Open Questions
Open tasks
Change checklist