-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
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
Add Http2 support #104
Comments
This item seemed to tagged to 0.9.0.RELEASE. Any idea where I can find the release schedule for this? Thanks |
We will work on that around Q2 - We haven't set a date but it should align with Spring Framework 5.1 work as well. We're looking pretty much to this indeed ( see reactor netty roadmap from S1P here https://speakerdeck.com/smaldini/springoneplatform-2017-reactor-now-and-tomorrow) ! |
@smaldini Can you please share if any progress is being made in this area? |
@thekalinga you can take a look here https://github.com/reactor/reactor-netty/blob/master/src/test/java/reactor/netty/http/HttpTests.java#L496 |
@violetagg Thanks for that. Do u have any idea when the development on this item might start & any target you have in mind for completion? |
What do you mean? |
@violetagg Sorry for my ignorance. I dont have much idea about the internal apis created in this project to support HTTP2 API. Is it fair to say 0.8.0 will contain full HTTP2 support? |
yes |
Hi, Which is the release date for 0.8.0? |
@medalliaerlich We are currently work towards M1, what do you want to see as HTTP/2 support in 0.8? Just supporting HTTP/2 protocol, or manipulating the streams etc. Thanks, |
We are planning on using Spring Cloud Gateway which is using Reactor Netty, and are waiting for release 0.8. Please check thread spring-cloud/spring-cloud-gateway#7 |
HTTP/2 support for HttpServer available as part of 0.8.0.M1 |
HTTP/2 for the server is available with Reactor Netty 0.8.x |
Wishlist item for Http2 support. Seems based on keepalive support that reused connections are possible.
The text was updated successfully, but these errors were encountered: