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

PUSH_PROMISE Stream Priority #75

Closed
jasnell opened this issue Apr 25, 2013 · 1 comment
Closed

PUSH_PROMISE Stream Priority #75

jasnell opened this issue Apr 25, 2013 · 1 comment

Comments

@jasnell
Copy link
Contributor

@jasnell jasnell commented Apr 25, 2013

The current draft (-02) says, "The endpoint establishing a new stream can assign a priority for the stream."

However, the spec does not define how a stream established using PUSH_PROMISE can assign the priority for a stream, nor does the spec discuss whether the notion of stream priority applies to push streams.

The spec currently states that PUSH_PROMISE is followed later on by a HEADERS frame.

If priority applies to push streams, then we need to add that priority can be assigned by allowing the use of a HEADERS+PRIORITY frame. Otherwise, we need to clarify the spec text to say that push streams have no priority.

@mnot
Copy link
Member

@mnot mnot commented Jun 13, 2013

Discussed at SF Interim.

Default for streams is 1/2 way through. If priority is not assigned through other means, pushed streams are assumed to inherit the priority of the associated request (minus one, priority-wise).

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

No branches or pull requests

3 participants