You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, I wondered, what does this mean for this module? Will it evolve into an HTTP/2 module over time? Will it get additional support? Will it stay a pure SPDY module? Does it work already for HTTP/2 as well? …?
As said before: Please don't get this question wrong, I really value your work on this module, and I definitely don't want to bash it.
The text was updated successfully, but these errors were encountered:
This really depends on nodejs/node#589 and nodejs/node#4 . First one is required because of ALPN that is used for advertising HTTP2 support. The second one will tell where this module would live.
First of all: I highly appreciate this module and use it in several projects :-)
So, please don't get this question wrong: It's not meant to be harshly or impolite, it just came to my mind this evening.
Today, the Chromium project has announced to drop support for SPDY in early 2016, as HTTP/2 will then be mature enough.
So, I wondered, what does this mean for this module? Will it evolve into an HTTP/2 module over time? Will it get additional support? Will it stay a pure SPDY module? Does it work already for HTTP/2 as well? …?
As said before: Please don't get this question wrong, I really value your work on this module, and I definitely don't want to bash it.
The text was updated successfully, but these errors were encountered: