reactor
WIP - HTTP3 migration
⚠️ Still in progress
- creating config for http3, made an abstract class of the configuration and set the default min values in the streams based on the incubator project
- plan is to create a structure similar to the abstract class
QuicServerandQuicServerBindfor Http3 ( let me know if you have any other suggetions).
@fokion Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
@fokion I need to take a look first at Netty HTTP3 codec. I haven't had time to think about a possible implementation. I'll try to find time next week to have at least rough idea. Things that we need to think in advance like pros/cons: the current HTTP server supports configuring the protocol version so that it is easy for users to switch between different HTTP versions. Do we want to think in that direction for HTTP/3 (if it is at all possible)? Or it is more likely that we want a new HTTP/3 server abstraction?
I was aiming at the moment to abstract it on top of Quic and make it working as a first step. Maybe it is better as you say to utilise the http abstractions. Will continue at the moment on this path to see what can be achieved and then review what we have and maybe with your direction adjust it.
@fokion @pderop Some very rough POC. Tell me what you think. https://github.com/reactor/reactor-netty/tree/http3-server