- From: Michael Nordman <michaeln@google.com>
- Date: Tue, 23 Sep 2008 11:52:39 -0700
A fallback entry is paired with a url namespace. The fallback resource is cached at manifest update time. If a request that matches the namespace results in a server or network error, the fallback resource is returned in its place. In the current draft of the spec, this is mired together with 'opportunistic caching', such that if the request were to succeed the response would be cached for later use. There is a proposal to decouple the 'fallback' behavior from the 'autocaching' behevior. Hope this helps. On Tue, Sep 23, 2008 at 10:48 AM, Christian Biesinger <cbiesinger at gmail.com>wrote: > Hi, > > I was reading > http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html > today and got a question about it... how exactly are fallback entries > working? I can't quite find a part of the spec that describes that. Or > even what they really are. > > Thanks, > -christian > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20080923/9c2a45dc/attachment.htm>
Received on Tuesday, 23 September 2008 11:52:39 UTC