Repository navigation
The future of HTTP in Node #2481
Description
Activity
I think http2 would be positively received, though would have lots and lots of review comments. But there isn't anybody around with the time. @ronkorving, if you wonder about starting the work, I'd suggest doing it, and PRing early for feedback.
IIRC, this has come up in TC meetings.
+1 It'd definitely be a big plus to have support for HTTP/2 baked into Node, especially considering that it has been standardized.
At the very least, it'd be nice to eventually get a clearer understanding of where HTTP/2 fits into the roadmap, if at all.
If I'm reading correctly, this pretty much gets summed up in the document @sam-github linked in the following paragraph (pasting here for easy reference).
Conclusion: We should start an issue in NG about the core modules/modernity stuff. We should publicly state that we’re interested in supporting HTTP/2 in the related issue thread, although we’re not sure about implementation strategy and want to see experiments.
The HTTP2 issue has come up several times before. It's definitely on the list of things we want, just no one has had the time to get to it yet. It's a rather large feature, that would take a lot of effort and careful review to get it right.
@indutny wrote node-spdy, which could be a good starting point.
It probably would be a good starting point (there's also https://www.npmjs.com/package/http2 btw). Given that the conversation has already taken place and a policy has been set, I will close this issue. If a conversation still is warranted, I'll happily re-open the issue. Thank you all for the feedback.
GIven that HTTP 2 has been standardized and given the fact that Node offers HTTP server and client API, at what point will it make sense to incorporate HTTP 2 into the stack?
Perhaps HTTP could be externalized, but in any case, I'm hoping to spark the conversation: When will Node take HTTP 2 as seriously as HTTP 1?
Thank you.