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

STREAM_ID_BLOCKED and distinguishing unidir/bidir #979

Closed
larseggert opened this issue Dec 1, 2017 · 4 comments
Closed

STREAM_ID_BLOCKED and distinguishing unidir/bidir #979

larseggert opened this issue Dec 1, 2017 · 4 comments
Labels
invalid A duplicate, overcome-by-events, ill-formed, or off-topic issue, or a question better asked on-list.

Comments

@larseggert
Copy link
Member

Now that we have unidirectional streams, how is the receiver of a STREAM_ID_BLOCKED frame supposed to tell which stream type to send a MAX_STREAM_ID for? Or is there an assumption here that raising MAX_STREAM_ID applies to both unidir and bidir streams?

@ianswett
Copy link
Contributor

ianswett commented Dec 1, 2017

A given stream ID refers to exactly one stream, which is either uni or bidi, not both.

@larseggert
Copy link
Member Author

Right, but since STREAM_ID_BLOCKED doesn't contain an ID, the receiver doesn't know which limit to raise. When you receive a MAX_STREAM_ID, you know for which type it is, but when you receive a STREAM_ID_BLOCKED, you don't.

@MikeBishop
Copy link
Contributor

#927 / #928 already addresses this, albeit as an accidental by-product.

@larseggert
Copy link
Member Author

Perfect, thanks

@mnot mnot added the invalid A duplicate, overcome-by-events, ill-formed, or off-topic issue, or a question better asked on-list. label Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid A duplicate, overcome-by-events, ill-formed, or off-topic issue, or a question better asked on-list.
Projects
None yet
Development

No branches or pull requests

4 participants