Add WebTransport client (wt_* API)#857
Merged
Merged
Conversation
Mirrors the WebSocket ws_* API over HTTP/3 or HTTP/2 via the webtransport library.
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
1 participant
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.
Adds a wt_* client API mirroring the WebSocket ws_* API, so code switches by swapping the ws_ prefix for wt_. Runs over HTTP/3 (default) or HTTP/2 via the webtransport library, with no custom wire framing so it interoperates with any WebTransport server.
One session multiplexes many streams (wt_open_stream, wt_stream_send/recv, datagrams) like HTTP/2; wt_send/wt_recv use a persistent default stream for ws parity. Request path and headers are checked for CR/LF/NUL and a buffer cap bounds unread data. Includes the WebTransport guide (client and server side) and tests.