-
-
Notifications
You must be signed in to change notification settings - Fork 813
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
Open new HTTP/2 connections when stream space is exhausted. #283
Comments
I would like to work on this. |
Opens new http2 connections when no more stream IDs are available Handle this by catching the exception `NoAvailableStreamIDError` thrown by h2-hyper.
Is this actually an issue for us?
|
Stream space is number of requests on a single connection, since each request requires its own stream. The concurrent streams limit is the number of requests you're allowed to have outstanding before making a new request. |
OK, I think we've got a shared understanding then. What made me think about whether this is a practical issue is this: Essentially, we can only get a |
It's not likely in everyday usage but it's a part of being a consumer of the |
We do about 1 million requests per day to a single host (APNS) in our application, so to me it doesn't seem too unrealistic to hit this limit, if a connection stays open for some time. |
Believe this to now be resolved in the 0.13.dev0 pre-release. |
http://http2.github.io/http2-spec/index.html#StreamIdentifiers "Long-lived connections can result in an endpoint exhausting the available range of stream identifiers. A client that is unable to establish a new stream identifier can establish a new connection for new streams. "
Somewhat related to #282
The text was updated successfully, but these errors were encountered: