W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2009

[whatwg] Cache Manifest: why have NETWORK?

From: Michael Nordman <michaeln@google.com>
Date: Wed, 23 Sep 2009 11:09:03 -0700
Message-ID: <fa2eab050909231109m56d74ba6p77522b08ee841e78@mail.gmail.com>
For cases where you don't want to, or can't,  'fallback' on a cached
resource.
ex 1.

http://server/get/realtime/results/from/the/outside/worldCreating a fallback
resource with a mock error or empty response is busy work.

ex 2.

http://server/change/some/state/on/server/side?id=x&newValue=y
Ditto

On Wed, Sep 23, 2009 at 2:47 AM, Anne van Kesteren <annevk at opera.com> wrote:

> If you use a fallback namespace it will always try to do a network fetch
> before using the fallback entry so why is there a need for a NETWORK entry
> in the cache manifest?
>
>
> --
> Anne van Kesteren
> http://annevankesteren.nl/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090923/9fda9467/attachment-0001.htm>
Received on Wednesday, 23 September 2009 11:09:03 UTC

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