quic: add scaffolding for Web Transport API #52628
Draft
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
Will be the JS API for QUIC
jasnell
added
the
quic
|
@jasnell Thank you very much for your contribution to the integration of http/3 in node js! Can you please tell me approximately what percentage of the implementation of HTTP/3 for node js has been completed? |
|
@jasnell Does this mean that Web Transport will be the way to use QUIC in Node.js, so no direct-QUIC support? |
|
Still not determined (both in terms of completion or exactly how QUIC will be exposed) |
|
If WebTransport is a moving target why not a replacement for the original API? By bringing back a transport layer |
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.
Will be the JS API for QUIC ... Not exposed public yet... just starting to get the basics in.... lots more to do here and Web Transport API is still a moving target...