suave
suave copied to clipboard
Feature/http2
working on #279
Is this Branch already usable?
No yet, still working on it :)
On Mon, Oct 17, 2016 at 5:54 AM, Jochen Kühner [email protected] wrote:
Is this Branch already usable?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/SuaveIO/suave/pull/434#issuecomment-254163901, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIl_KStys4aU1blGJwGAFILIB-NP381ks5q00XngaJpZM4IZGKI .
Ademar Gonzalez +1-647-891-3606 http://ademar.name https://github.com/ademar
🎆 🎊
Will you also support Server Side push?
@jogibear9988 It should be possible.
Any News to the HTTP2 support?
Sorry, I have gotten sidetracked with other work; also kind of waiting to see if SslStream is going to have ALPN support which is required by all browsers.
related: https://github.com/dotnet/corefx/issues/4721 - SslStream ALPN support
do you also know https://github.com/Matthias247/http2dotnet
Hey @jogibear9988 , thanks for mentioning my library. Yes, it's exactly intended to enable other applications or frameworks to speak HTTP/2 in an easy fashion. It should be integrateable into Suave (or other web frameworks). I'd be happy if anybody is interested in experimenting with it! And I also appreciate any feedback.
Regarding the state: The server side is in the meantime really well covered. From a feature side only push promises are missing, but these are not too important for most applications. From a performance point of view the scheduler for outgoing data is quite primitive, but it most likely still works better than lots of HTTP/1 setups. HTTPS of course only works with an ALPN enabled TLS library - which we are currently still missing in .NET Framework :'(
FYI: ALPN support for SslStream is implemented: https://github.com/dotnet/corefx/pull/24389