-
-
Notifications
You must be signed in to change notification settings - Fork 937
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
HTTP2 performance and multiple concurrency #88
Comments
That'd be interesting. We're currently using got, but not by much, so it might be easy to switch to http2 with possible http fallback. If there's a package that already handles this, lemme know (I don't know of any!). PR's are also welcome. |
Unfortunately there is no package that wraps this. I've created an Issue for GOT here: Otherwise, we would have to use Or create a new package. |
Ok seems that its gonna be easier to fix on the GOT side. However we might add here the |
@gunta we now use the same package that npm uses to make http requests (https://github.com/npm/npm-registry-client). Do you think this issue is still relevant? |
@zkochan Still relevant. They use Since it doesn't looks too difficult, we could hack something like this in the meantime: http://stackoverflow.com/questions/37653110/is-there-a-request-like-package-using-http2 |
I see. We can try to make a pull request to npm-registry-client. If they won't accept it, we can fork it and use the fork. |
Is this still relevant? Node 10 (and probably earlier releases) supports http2 internally (at least "experimental"). |
sure, would be nice to see if we get a performance boost with that library. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hi!
I'm currently using an internal npm registry.
Do you think it would be worth exploring the possibility of making this HTTP2 enabled?
This may allow for infinite concurrency with no penalty.
For example we could use this for server/client: https://github.com/molnarg/node-http2
The text was updated successfully, but these errors were encountered: