-
Notifications
You must be signed in to change notification settings - Fork 205
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
Mandate allowing peer to create enough unidirectional streams for HTTP and QPACK #2762
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's one nit which implies a design question; once that's settled one way or another, I'm happy with this.
It's acceptable but not ideal. Didnt we just remove a mandatory TP in some unrelated change? |
Also rebased to fix conflict. |
…P and QPACK As per #2100 (comment) HTTP MUST allow enough uni streams credits for mandatory streams (control, QPACK encoder/decoder, other mandatory extensions) but is not required to grant additional credits if the peer wastes them.
That is an exceptionally long sentence. But I think the text is correct. |
As per #2100 (comment) HTTP MUST allow enough uni streams credits for mandatory streams (control, QPACK encoder/decoder, other mandatory extensions) but is not required to grant additional credits if the peer wastes them.
This is the companion PR to #2529 updating the requirements in the HTTP draft, and together they fix #2100. I created a separate PR since it touches -http instead of -qpack, so it doesn't get blocked by the QPACK refactoring.