Feature/http2 #434
Feature/http2 #434
Conversation
|
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]
Ademar Gonzalez |
|
🎆 🎊 |
|
Will you also support Server Side push? |
|
@jogibear9988 It should be possible. |
* get31bit now works on both little-endian and big-endian architectures * get31bit now explicitly expects its byte[] arg in network byte order * stream identifiers now encode correctly * poke16 function now writes bytes in network byte order (big-endian) * poke32 function now writes bytes in network byte order (big-endian)
Fix a few endianness bugs on HTTP/2 branch
|
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 , 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: dotnet/corefx#24389 |
working on #279