[whatwg] Google Gears and HTML5

[Chris Prince]

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