Merged
Conversation
Revise the WebTransport explainer to add in all the new features and capabilities since the last update in Oct 2021
Expanded the proposed solution section to include subprotocol negotiation details and added a note on additional use cases and security considerations.
Updated the explainer document to clarify WebTransport features and use cases, including new sections on connection management, stream handling, and datagram management.
jan-ivar
requested changes
Jan 21, 2026
Member
jan-ivar
left a comment
jan-ivar
left a comment
There was a problem hiding this comment.
Overall much improved, thanks! Some nits, feedback on examples. But I'd like to keep the existing problem statement, if possible.
Comment on lines
+72
to
+74
| value: new Uint8Array([0xed, 0xb0, 0x3e, ...]) // For local dev | ||
| }], | ||
| headers: { 'Authorization': 'Bearer <token>' } |
Member
There was a problem hiding this comment.
Great examples! But I'd prefer they be slightly more complete, as we have some feedback that people struggle to understand this part otherwise
Comment on lines
84
to
92
| // Receiving a server-initiated unidirectional stream | ||
| const reader = transport.incomingUnidirectionalStreams.getReader(); | ||
| const { value: stream } = await reader.read(); | ||
| const data = await new Response(stream).arrayBuffer(); | ||
|
|
||
| // Creating a bidirectional stream | ||
| const biStream = await transport.createBidirectionalStream(); | ||
| const biWriter = biStream.writable.getWriter(); | ||
| await biWriter.write(new TextEncoder().encode("Hello Server")); |
Member
There was a problem hiding this comment.
I'd prefer we use the streams spec as intended with pipeTo like example 7 instead of getReader and getWriter. I can also do this in a follow-up.
Applies throughout
Updated references from 'transport' to 'wt' for consistency and clarity. Enhanced explanations regarding WebTransport's capabilities and use cases.
Co-authored-by: Jan-Ivar Bruaroey <jan-ivar@users.noreply.github.com>
jan-ivar
approved these changes
Jan 21, 2026
wilaw
added
Editors can integrate
Editorial
github-actions bot
added a commit
that referenced
this pull request
Jan 21, 2026
SHA: 62374ed Reason: push, by jan-ivar Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The explainer was last updated 3 years ago. This PR updates it to include new features and capabilities added since that time.
Fixes #694