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


From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 21 Feb 2013 16:02:04 -0800
Message-ID: <CABkgnnUcOFY=FtESWyhmayUvFvz===w=_KndNjM_diLkcSOQSw@mail.gmail.com>
To: Roberto Peon <grmocg@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
On 21 February 2013 15:54, Roberto Peon <grmocg@gmail.com> wrote:
> I mean that SYN_STREAM has a priority, which is mandatory because without it
> the browser won't trust the server-side to do the right thing.


> SYN_REPLY doesn't have one, because it doesn't need to declare priority--
> the SYN_STREAM already did that, and it is almost always a waste to include
> a priority field in SYN_REPLY.

Agree.  So what does SYN_REPLY actually do then?

> I intend to consume a flag value which indicates that the semantic-frame is
> longer than the current frame. The delta code already does this. I think I
> stuck that in the SPDY/4 stuff (so it could be pulled from there, unless I'm
> misremembering).

A "To be continued..." flag sounds about right.
Received on Friday, 22 February 2013 00:02:31 UTC

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