W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2007

[whatwg] Google Gears and HTML5

From: Chris Prince <cprince@google.com>
Date: Tue, 9 Oct 2007 00:58:08 -0700
Message-ID: <cd580da00710090058p1dbe44cel667372238fcb5c57@mail.gmail.com>
On 10/9/07, Ian Hickson <ian at hixie.ch> wrote:
> On Fri, 1 Jun 2007, Chris Prince wrote:
> > That is correct.  Gears starts serving a manifest's resources only when
> > everything has been successfully downloaded.  If it gets a 404 it will
> > try again later.
>
> So how does a page, once cached, stop being cached? There doesn't seem to
> be a way to end the caching. In HTML5's model, you have to leave a blank
> manifest file forever (or until all your users have been weened off the
> old cache manifest) for applications to lose their cache association.

The Gears LocalServer module has remove*Store() methods that will end
the caching.  Serving a blank manifest works in the Gears model as
well.

--Chris
Received on Tuesday, 9 October 2007 00:58:08 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:37 UTC