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

The future of HTTP in Node #2481

Closed
ronkorving opened this issue Aug 21, 2015 · 7 comments
Closed

The future of HTTP in Node #2481

ronkorving opened this issue Aug 21, 2015 · 7 comments
Labels
http Issues or PRs related to the http subsystem.

Comments

@ronkorving
Copy link
Contributor

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.

@brendanashworth brendanashworth added the http Issues or PRs related to the http subsystem. label Aug 21, 2015
@pyrossh
Copy link

pyrossh commented Aug 21, 2015

I don't think node might be adding this immediately into the core but their are some awesome libraries that support this koala and this SPDY.
Well it seems golang has got http2 in the testing phases https://http2.golang.org/

@sam-github
Copy link
Contributor

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.

@adalinesimonian
Copy link

+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.

@adalinesimonian
Copy link

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.

@Qard
Copy link
Member

Qard commented Aug 21, 2015

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.

@ronkorving
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
http Issues or PRs related to the http subsystem.
Projects
None yet
Development

No branches or pull requests

6 participants