- From: Christian Biesinger <cbiesinger@gmail.com>
- Date: Wed, 24 Sep 2008 14:47:30 +0200
Ah thanks. I missed the 5.7.5.1/4 part of the spec. -christian On Tue, Sep 23, 2008 at 8:52 PM, Michael Nordman <michaeln at google.com> wrote: > 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 > >
Received on Wednesday, 24 September 2008 05:47:30 UTC