W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2013

Design Issue: PUSH_PROMISE and Stream Priority

From: James M Snell <jasnell@gmail.com>
Date: Thu, 25 Apr 2013 11:03:08 -0700
Message-ID: <CABP7Rbf_hZ036vUs4LNTrGQ91kft2_97aV-9Gi2KVJnUJphbNA@mail.gmail.com>
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>

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.
Received on Thursday, 25 April 2013 18:03:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:12 UTC