Repository navigation
Experimental WebTransport support - #162
Draft
fpseverino wants to merge 5 commits into
Draft
fpseverino wants to merge 5 commits into
fpseverino wants to merge 5 commits into
Conversation
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
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.
This PR adds the necessary utilities to the public API to support WebTransport over HTTP/3 sessions (following draft-ietf-webtrans-http3-16).
Since Extended CONNECT and HTTP Datagrams are already supported, what is missing is a way to open QUIC streams to the client and receive them. SwiftNIO HTTP/3 currently does not allow to open and intercept incoming QUIC streams on an HTTP/3 connection, but I’ve opened a pull request there to add support for it.
Methods for opening streams have been added to
NIOHTTPServer.Connection, and theAsyncStreams that receive incoming streams can be accessed viaNIOHTTPServer.Reader. Everything is hidden behind the"UnstableWebTransport"package trait.I’ve also included an example of how to set up a WebTransport server using
swift-http-serverand these new APIs.I still regard these APIs as experimental. I have opened this draft PR so that we can start a discussion on the subject, having a rough idea of the API.
There are still many WebTransport features, such as Flow Control, that have not been implemented. The features implemented in this PR are only the essential ones.