WebSockets: add spec #624
Merged
WebSockets: add spec #624
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Specifies the WebSockets transport with notes on certificates, multiplexing, etc. Fixes #594
|
One improvement we could make here is to use the protocols arg to specify the connection encrypter (e.g. This would save a bunch of multistream-select round trips. |
SgtPooki
reviewed
Aug 13, 2024
p-shahi
reviewed
Sep 10, 2024
Co-authored-by: Prithvi Shahi <[email protected]>
|
It's been a couple of months now so If there are no further comments here, I'm going to merge this at the end of the week. |
achingbrain
commented
Oct 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Specifies the WebSockets transport with notes on certificates, multiplexing, etc.
It tries to document the current state of WebSocket transport with the exception of the
http-pathwhich I don't think is implemented anywhere.A follow up PR to this PR will attempt to address the double-encryption problem as it's worthy of it's own discussion.
Please suggest an edit to the Interest Group if you want to be added.
Fixes #594