- From: <bugzilla@jessica.w3.org>
- Date: Sat, 12 Nov 2011 01:01:51 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14702 --- Comment #14 from Yehuda Katz <wycats@gmail.com> 2011-11-12 01:01:50 UTC --- As to HTTP caches, there are several issues that are addressed by the application cache: * HTTP caches are not atomic, which means that individual assets or pages can be evicted separately from each other. This is very important behavior for offline web sites. * Browsers are not required to serve pages offline that are in HTTP caches, and their current behavior is unreliable and spotty from a user perspective. Efforts to specify this behavior more rigorously would probably be more work (and less in scope) than the proposed improvement to app cache. Application cache provides a way to tell the user agent that a series of assets should be inserted in the cache together, evicted rarely and atomically, and served when offline. The use-case for this feature takes advantage of all of those improvements over normal HTTP caching semantics. -- Configure bugmail: http://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 Saturday, 12 November 2011 01:01:52 UTC