eclipse-vertx
Feature/http3 support 5.x
Motivation This PR introduces support for HTTP/3 in Vert.x, leveraging the existing HTTP/3 facilities provided by Netty. The motivation behind this change is to bring the latest HTTP protocol version to Vert.x, allowing developers to take advantage of the performance improvements and new features that HTTP/3 offers, such as reduced latency, improved security, and better handling of packet loss.
Currently, the PR focuses on adding HTTP/3 support for the client side only. This is the first step towards full HTTP/3 integration in Vert.x. The server-side implementation will be addressed in a subsequent PR, and comprehensive testing will be conducted at that stage.
By enabling HTTP/3 support on the client side, this change positions Vert.x to remain a competitive and modern toolkit for reactive applications. It allows developers to begin experimenting with and utilizing HTTP/3 in their client applications, paving the way for broader adoption once server-side support is complete.
Co-Authored: @zekronium
@vietj Why not have it as an optional dependency. Might take while, whilst other projects are already using it such as netty reactor
Do you have some numbers to share? we tested HTTP/3 for internal networking (internal RPC) and it shows it performant bad than HTTP/2,
@imz87 I had to make some internal changes, you should rebase this branch over latest master
@imz87 I had to make some internal changes, you should rebase this branch over latest master @vietj , sure, I'll rebase my branch onto the latest master.
Do you have some numbers to share? we tested HTTP/3 for internal networking (internal RPC) and it shows it performant bad than HTTP/2,
@He-Pin I haven't tested HTTP/3 against anything yet, so I don't have any numbers or statistics to share at this time. I just added Http3Test.java, which is similar to Http2Test.java and serves as a kind of unit test.
@imz87 I had to make some internal changes, you should rebase this branch over latest master @vietj , sure, I'll rebase my branch onto the latest master.
@vietj , I just rebased onto the latest master.
Hi @vietj ,
I noticed that there's a NetSocket implementation for HTTP/2, and it seems to be used for WebSocket as well. Is something similar required for HTTP/3? Specifically, would we need a WebSocket based on an HTTP/3 connection?
Thanks, Iman
@imz87 yes this is needed, the main use case is HTTP CONNECT that tunnels a NetSocket.
@imz87 yes this is needed, the main use case is HTTP CONNECT that tunnels a NetSocket.
Ok, thanks for your response.
Looking forward to this so I can switch from websockets to http3 streams.
Looking forward to this so I can switch from websockets to http3 streams.
Great to hear! We're excited for you to try it out.