We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
We finalized our implementation in Vertx for HTTP3 and mainly are waiting for this to land on 4.2.
Considering browsers and quite alot of services or atleast FE’s support it, QUIC itself seems mature enough aswell.
is there anything thats holding this back from landing on 4.2?
The text was updated successfully, but these errors were encountered:
@zekronium I am not sure yet if it will be merged into 4.2 yet but we will have it depend on 4.2 for sure
Sorry, something went wrong.
@normanmaurer What is holding it back?
Do you have any performance sharing about HTTP/3 vs HTTP/2 with Netty, thanks @zekronium
No branches or pull requests
Hi,
We finalized our implementation in Vertx for HTTP3 and mainly are waiting for this to land on 4.2.
Considering browsers and quite alot of services or atleast FE’s support it, QUIC itself seems mature enough aswell.
is there anything thats holding this back from landing on 4.2?
The text was updated successfully, but these errors were encountered: