So if the content for a "fallback namespace" is cached, which should be if it starts with network connection and if server not explicitly use "no-cache/no-store" cache control, then it will always be used, from network or cache, and its mapping "fallback entry" will never be used, even if it's offline?
-----Original Message----- From: Shwetank Dixit [mailto:shweta...@opera.com] Sent: Tuesday, July 13, 2010 10:43 AM To: whatwg@lists.whatwg.org; Lianghui Chen Subject: Re: [whatwg] About bypassing caches for URLs listed in Fallback and/or Network section in a HTML5 Offline Web Application For 'fallback', it will try to load the resource normally, however, if the user is offline, that can't happen...so it will try to do it till a short while till it gives up (during that short while, if something is cached as part of the normal cache then it will use it), after which it will load the fallback resource wherever applicable. On Tue, 13 Jul 2010 19:56:49 +0530, Lianghui Chen <liac...@rim.com> wrote: > Thanks, but that means once Opera starts with network connected, it > won't detect whether network is offline for offline web applications. > Doesn't it somehow defeat the purpose of "fallback" resource? > > -----Original Message----- > From: Shwetank Dixit [mailto:shweta...@opera.com] > Sent: Tuesday, July 13, 2010 10:19 AM > To: Lianghui Chen; whatwg@lists.whatwg.org > Subject: Re: [whatwg] About bypassing caches for URLs listed in Fallback > and/or Network section in a HTML5 Offline Web Application > > At least in Opera, it will still respect the browser's normal cache > header. So the network section header will just bypass the application > cache, and will load normally like any other web page, which means > respecting (i.e, not bypassing) the normal cache. > > On Tue, 13 Jul 2010 19:28:55 +0530, Lianghui Chen <liac...@rim.com> > wrote: > >> >> Anyone has any comments? >> >> From: whatwg-boun...@lists.whatwg.org >> [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Lianghui Chen >> Sent: Monday, July 12, 2010 4:12 PM >> To: whatwg@lists.whatwg.org >> Subject: [whatwg] About bypassing caches for URLs listed in Fallback >> and/or Network section in a HTML5 Offline Web Application >> >> Hi, >> >> In spec HTML5 for offline web application >> (http://www.whatwg.org/specs/web-apps/current-work/#offline) chapter >> 6.6.6, item 3, 4, 5 state that for resources that is in online whitelist >> (or has wildcard whitelist), or fallback list, it should be fetched >> "normally". >> >> I would like to know does it mean the user agent (browser) should bypass >> its own caches (besides html5 appcache), like the WebKit cache and >> browser http stack cache? >> >> Best Regards >> Lyon Chen >> >> >> --------------------------------------------------------------------- >> This transmission (including any attachments) may contain confidential >> information, privileged material (including material protected by the >> solicitor-client or other applicable privileges), or constitute >> non-public information. Any use of this information by anyone other than >> the intended recipient is prohibited. If you have received this >> transmission in error, please immediately reply to the sender and delete >> this information from your system. Use, dissemination, distribution, or >> reproduction of this transmission by unintended recipients is not >> authorized and may be unlawful. > > -- Shwetank Dixit Web Evangelist, Site Compatibility / Developer Relations / Consumer Products Group Member - W3C Mobile Web for Social Development (MW4D) Group Member - Web Standards Project (WaSP) - International Liaison Group Opera Software - www.opera.com Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.