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

Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY

From: James M Snell <jasnell@gmail.com>
Date: Sun, 26 May 2013 08:31:12 -0700
Message-ID: <CABP7RbdUSLTN1YJDkigfqvMJw7hUh4Uv+CYSsFETn6N+EQ0NdA@mail.gmail.com>
To: Jeff Pinner <jpinner@twitter.com>
Cc: ChanWilliam(ι™ˆζ™Ίζ˜Œ) <willchan@chromium.org>, Roberto Peon <grmocg@gmail.com>, Patrick McManus <pmcmanus@mozilla.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
On May 26, 2013 7:31 AM, "Jeff Pinner" <jpinner@twitter.com> wrote:
>
[snip]
>
> So since we have frame specific flags now can we just use them and drop
to duplicated frame type so that only one frame is used for stream creation?
>
> 1. remove frame 0x08 HEADERS as duplicated
> 2. rename frame 0x01 from HEADERS+PRIORITY to HEADERS and indicate that
it is the only frame that may create a stream
> 3. add flag 0x02 PRIORITY to the HEADERS frame to indicate the first 4
bytes of the frame contain a priority field
> 4. add flag 0x04 CONTINUED to the HEADERS frame to indicate that the
headers block is split across a second frame which must be the next frame
sent on the wire
> 5. add a frame 0x02 PRIORITY that is 4 bytes long and must be sent only
on open streams
>
> a slightly different shade of shed :)

+1... This works for me.
Received on Sunday, 26 May 2013 15:31:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:11 UTC