- From: <bugzilla@jessica.w3.org>
- Date: Wed, 09 May 2012 10:23:16 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14702
Andrew Betts <andrew.betts@ft.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |andrew.betts@ft.com
--- Comment #34 from Andrew Betts <andrew.betts@ft.com> 2012-05-09 10:23:15 UTC ---
At the FT we effectively have an advanced variant of Tobie's 'Make a Blog work
offline' use case.
Pages of a news app can be expected to contain perishable content, which should
be refreshed on each visit if a network connection is available. However, in
enabling appCache, we are forced to have a page of highly dynamic content in
our cache, which is not acceptable and eliminates the use of appcache in the
conventional way as an option.
The way we solve this currently is using a similar method to that outlined by
Jake in comment 33. Our news pages *do not* include a manifest attribute on
the <html> tag, but instead have a hidden IFRAME that loads a dedicated
appcache loader resource, eg:
<iframe src='/appcacheloader.html'></iframe>
The appcacheloader.html file includes the manifest attribute on its <html>
element, but is otherwise an empty page, and isn't explicitly listed in the
manifest, so gets cached as a master entry, which we don't care about. This
allows us to ensure that we don't cache perishable content but still provide
fallbacks for it.
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 9 May 2012 10:23:22 UTC