Skip to content
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

Future of this module with respect to HTTP/2? #191

Closed
goloroden opened this issue Feb 9, 2015 · 2 comments
Closed

Future of this module with respect to HTTP/2? #191

goloroden opened this issue Feb 9, 2015 · 2 comments

Comments

@goloroden
Copy link
Contributor

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.

@indutny
Copy link
Collaborator

indutny commented Feb 9, 2015

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.

I think it'll be either support here, on in core.

@goloroden
Copy link
Contributor Author

Thanks for the very fast reply, and for clarifying things :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants