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.

Sign up for GitHub

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

Jump to bottom

Minimum concurrent stream value #186

Closed
igorlord opened this issue Jan 21, 2017 · 3 comments
Closed

Minimum concurrent stream value #186

igorlord opened this issue Jan 21, 2017 · 3 comments
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@igorlord
Copy link
Contributor

The specification allows endpoints to specify the maximum number of concurrent streams (MSPC), but should not the spec provide for the minimum value of MSPC that all endpoints must support? If the minimum is 1 (excluding "service" streams), it would be good for the spec to state so explicitly.
@igorlord igorlord changed the title Minimum concurrent streams requirment Minimum concurrent streams requirement Jan 24, 2017
@martinthomson martinthomson changed the title Minimum concurrent streams requirement Minimum concurrent stream value Jan 24, 2017
@martinthomson
Copy link
Member

Hmm, 1 is a valid value. The only value that doesn't make sense is 0. HTTP/2 permitted a value of 0, temporarily, but we don't have any way to change settings yet (see #50).

@martinthomson martinthomson added editorial An issue that does not affect the design of the protocol; does not require consensus. -transport labels Jan 24, 2017
@igorlord
Copy link
Contributor Author

igorlord commented Jan 24, 2017 •
edited

What you say: "1", do you include STREAM 1? If so, what does it say about clients not able to start data streams? It is useful?

If 1 does not include STREAM 1, does it mean we cannot do HTTP anymore? (Needs a minimum of 3 streams, plus STREAM 1).

@martinthomson martinthomson mentioned this issue Jan 24, 2017
Closed
@martinthomson
Copy link
Member

#421 killed this dead. Mostly. #456 would remove the only remaining wart, but that's not necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@martinthomson @igorlord