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.
The text was updated successfully, but these errors were encountered:
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).
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.
The text was updated successfully, but these errors were encountered: