You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2020. It is now read-only.
possibly but the thing to remember is that QUIC != HTTP/3. QUIC is the transport protocol while HTTP/3 is the application protocol that layers on top. Currently we've been focusing on just the QUIC specific API. Given how much trouble the HTTP/2 compatibility API has been, I'm not too keen on doing too much in core around a compat API for HTTP/3, and would almost prefer to leave that to framework implementations like fastify, express, etc, should they decide to adopt HTTP/3.
When can I use http3 to start the server in nodejs? Is there an approximate timetable?
masx200
changed the title
Can quic provide APIs similar to HTTP1.1, making it easier to upgrade older servers to HTTP3? And save backward compatibility.
Can HTTP3 provide APIs similar to HTTP1.1, making it easier to upgrade older servers to HTTP3?
Mar 14, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Can http3 provide APIs similar to HTTP1.1, making it easier to upgrade older servers to HTTP3? And save backward compatibility.
The goal is to make minimal code changes to upgrade the server from http1.1 to http3.
to Make Internet services more accessible and faster.
The text was updated successfully, but these errors were encountered: