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

Consider eliminating PRIORITY region from HEADERS #72

Closed
MikeBishop opened this issue Dec 5, 2016 · 2 comments
Closed

Consider eliminating PRIORITY region from HEADERS #72

MikeBishop opened this issue Dec 5, 2016 · 2 comments
Labels
-http design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list.

Comments

@MikeBishop
Copy link
Contributor

In HTTP/2, the HEADERS frame "opened" a stream. In this mapping, any frame can appear first on a stream, since the stream "opens" at the QUIC layer. Do we still need the PRIORITY region in HEADERS, or should implementations just send a PRIORITY frame if they want to declare prioritization?
@MikeBishop
Copy link
Contributor Author

Done in current draft.

@MikeBishop
Copy link
Contributor Author

For future reference, PRIORITY needs to move off-stream because changes aren't necessarily commutative. [A->B, A->C] produces a different result than [A->C, A->B], for a trivial example.

@mnot mnot added the design An issue that affects the design of the protocol; resolution requires consensus. label Apr 19, 2017
@mnot mnot added the has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list. label May 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-http design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mnot @MikeBishop