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

section 5.1 PRIORITY frame and idle state clarification #667

Closed
Scottmitch opened this issue Dec 9, 2014 · 2 comments
Closed

section 5.1 PRIORITY frame and idle state clarification #667

Scottmitch opened this issue Dec 9, 2014 · 2 comments

Comments

@Scottmitch
Copy link

section 5.1 has the following text:

idle:
All streams start in the "idle" state. In this state, no frames
have been exchanged.

It seems like PRIORITY frames can be sent/received in the IDLE state without causing a state transition as illustrated in figure 2. If I am interpreting this correctly then the no frames have been exchanged statement is not necessarily correct if PRIORITY frames have been exchanged.

@Scottmitch
Copy link
Author

Any thoughts for the preferred way to clarify this? Removing the In this state, no frames have been exchanged. statement will be sufficient but we may then be missing the original meaning this sentence was meant to convey.

@martinthomson
Copy link
Collaborator

Closed by #684

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants