W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

Re: Push and Caching

From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 22 Aug 2014 10:57:33 -0700
Message-ID: <CABkgnnW5NMo8ZuxzHVb+z=9z6NXDZf40iQY75qDcBNfzOWAdeQ@mail.gmail.com>
To: Mike Bishop <Michael.Bishop@microsoft.com>
Cc: Mark Nottingham <mnot@mnot.net>, Patrick McManus <mcmanus@ducksong.com>, William Chow <wchow@mobolize.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 22 August 2014 10:30, Mike Bishop <Michael.Bishop@microsoft.com> wrote:
> "While the stream identified by the promised stream ID is still open" - meaning that as long as the client has asked for it before the server has finished sending it?  That's a fairly small amount of time, particularly if the resource is very small, but sounds like a good starting point.

I'm sure that clients can fail to notice the END_STREAM flag for as
long as they need to in order to ensure that the various races resolve
in the right way...

Trying to determine how long the window is after END_STREAM arrives in
which clients can consider the response validated is nasty.  I don't
know how to finesse this other than turning a blind eye to small
violations, the likes of which you (and Firefox too) are committing in
this regard.
Received on Friday, 22 August 2014 17:58:00 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:10 UTC