-
-
Notifications
You must be signed in to change notification settings - Fork 36.5k
Split HTTP/3 module out from QUIC #63995
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
Open
pimterry
wants to merge
11
commits into
nodejs:main
Choose a base branch
from
pimterry:http3
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+4,791
−4,187
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
b9cffb3
quic: create standalone Http3Session APIs around QUIC
pimterry 35691fa
quic: split out full http3 module with separate request() API
pimterry 92f5d2c
quic: use 'kApplication' not ALPN to explicitly connect QUIC to H3
pimterry 0efd303
quic: make Applications optional, with raw stream support in sessions
pimterry dd48939
quic: move HTTP/3 protocol machinery into node:http3
pimterry 55450be
quic: bring in a related performance optimizations en route
pimterry 58eae6b
quic: move HTTP/3 event emit logic into Http3Application
pimterry 33e84b7
quic: use http3Binding to drop header & priority stream logic from QUIC
pimterry ec1dc6e
quic: add docs for http3 module, update quic docs & internal README
pimterry 9d175ef
quic: move HTTP/3 APIs back inside node:quic
pimterry 4882960
quic: resolve various small further issues & omissions in HTTP/3 API
pimterry File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Do we really need separate connect and listen variants for http3?
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.
Strictly speaking, no.
Those two APIs create a auto-H3 client/server with sensible H3 defaults that automatically wires up the h3 application. It's roughly the equivalent to the current auto-HTTP3 support. But with this PR you can now use
new Http3Session(quicSession)to dynamically create an HTTP/3 session on top of QUIC instead, so a separate server/client API is no longer necessary.It is mildly more fiddly this way: you have to manually create the H3 session every time, and we wouldn't offer a way to set up any HTTP/3 specific defaults (e.g. ALPN) for you. Given we now intend this only for low-level use cases that's fine though, it gives you more control en route anyway.
There is one practical limitation right now: you can't do server 0RTT with dynamic attach like this (because by the time
sessionevent fires on the server to attach, that's been partially processed already). That is fixable I think, it's just a separate step I was going to leave until later. I could investigate that further within this PR instead though, and then if there's a good solution then we could drop these with no practical downside.