[html5] r3189 - [] (0) Update the appcache mechanism for handling low-storage-space cases.
whatwg at whatwg.org
whatwg at whatwg.org
Thu Jun 4 15:29:00 PDT 2009
Author: ianh
Date: 2009-06-04 15:28:58 -0700 (Thu, 04 Jun 2009)
New Revision: 3189
Modified:
index
source
Log:
[] (0) Update the appcache mechanism for handling low-storage-space cases.
Modified: index
===================================================================
--- index 2009-06-04 19:24:28 UTC (rev 3188)
+++ index 2009-06-04 22:28:58 UTC (rev 3189)
@@ -776,8 +776,9 @@
<li><a href=#matching-a-fallback-namespace><span class=secno>6.9.5 </span>Matching a fallback namespace</a></li>
<li><a href=#the-application-cache-selection-algorithm><span class=secno>6.9.6 </span>The application cache selection algorithm</a></li>
<li><a href=#changesToNetworkingModel><span class=secno>6.9.7 </span>Changes to the networking model</a></li>
- <li><a href=#application-cache-api><span class=secno>6.9.8 </span>Application cache API</a></li>
- <li><a href=#browser-state><span class=secno>6.9.9 </span>Browser state</a></ol></li>
+ <li><a href=#expiring-application-caches><span class=secno>6.9.8 </span>Expiring application caches</a></li>
+ <li><a href=#application-cache-api><span class=secno>6.9.9 </span>Application cache API</a></li>
+ <li><a href=#browser-state><span class=secno>6.9.10 </span>Browser state</a></ol></li>
<li><a href=#history><span class=secno>6.10 </span>Session history and navigation</a>
<ol>
<li><a href=#the-session-history-of-browsing-contexts><span class=secno>6.10.1 </span>The session history of browsing contexts</a></li>
@@ -50019,8 +50020,16 @@
<a href=#cache-host>cache host</a>, and potentially given a new <a href=#concept-appcache-master title=concept-appcache-master>master</a> resource, the user
agent must run the following steps:</p>
- <ol><li>
+ <ol><li><p>Optionally, wait until the permission to start the cache
+ update process has been obtained from the user. This could include
+ doing nothing until the user explicitly opts-in to caching the
+ site, or could involve prompting the user for permission. (This
+ step is particularly intended to be used by user agents running on
+ severely space-constrained devices or in highly privacy-sensitive
+ environments).<li>
+ <li>
+
<p>Atomically, so as to avoid race conditions, perform the
following substeps:</p>
@@ -50308,10 +50317,9 @@
may skip this URL.</p>
<p class=note>This is intended to allow user agents to expire
- resources not listed in the manifest (other than those in the
- manifest itself) from the cache. Generally, implementors are
- urged to use an approach that expires lesser-used resources
- first.</p>
+ resources not listed in the manifest from the cache. Generally,
+ implementors are urged to use an approach that expires
+ lesser-used resources first.</p>
</li>
@@ -50786,9 +50794,24 @@
</div>
+ <h4 id=expiring-application-caches><span class=secno>6.9.8 </span>Expiring application caches</h4>
- <h4 id=application-cache-api><span class=secno>6.9.8 </span>Application cache API</h4>
+ <p>As a general rule, user agents should not expire application
+ caches, except on request from the user, or after having been left
+ unused for an extended period of time.</p>
+ <p>Implementors are encouraged to expose application caches in a
+ manner related to HTTP cookies, allowing caches to be expired
+ together with cookies and other origin-specific data. Application
+ caches and cookies have similar implications with respect to privacy
+ (e.g. if the site can identify the user when providing the cache, it
+ can store data in the cache that can be used for cookie
+ resurrection).</p>
+
+
+
+ <h4 id=application-cache-api><span class=secno>6.9.9 </span>Application cache API</h4>
+
<pre class=idl>interface <dfn id=applicationcache>ApplicationCache</dfn> {
// <a href=#concept-appcache-status title=concept-appcache-status>update status</a>
@@ -50992,7 +51015,7 @@
</table></div>
- <h4 id=browser-state><span class=secno>6.9.9 </span>Browser state</h4>
+ <h4 id=browser-state><span class=secno>6.9.10 </span>Browser state</h4>
<dl class=domintro><dt><var title="">window</var> . <code title=dom-navigator><a href=#dom-navigator>navigator</a></code> . <code title=dom-navigator-onLine><a href=#dom-navigator-online>onLine</a></code></dt>
@@ -70757,6 +70780,7 @@
Allan Clements,
Anders Carlsson,
Andreas<!-- mqmq87 -->,
+ Andrei Popescu,
Andrew Clover,
Andrew Gove,
Andrew Sidwell,
Modified: source
===================================================================
--- source 2009-06-04 19:24:28 UTC (rev 3188)
+++ source 2009-06-04 22:28:58 UTC (rev 3189)
@@ -57067,6 +57067,14 @@
<ol>
+ <li><p>Optionally, wait until the permission to start the cache
+ update process has been obtained from the user. This could include
+ doing nothing until the user explicitly opts-in to caching the
+ site, or could involve prompting the user for permission. (This
+ step is particularly intended to be used by user agents running on
+ severely space-constrained devices or in highly privacy-sensitive
+ environments).</p><li>
+
<li>
<p>Atomically, so as to avoid race conditions, perform the
@@ -57423,10 +57431,9 @@
may skip this URL.</p>
<p class="note">This is intended to allow user agents to expire
- resources not listed in the manifest (other than those in the
- manifest itself) from the cache. Generally, implementors are
- urged to use an approach that expires lesser-used resources
- first.</p>
+ resources not listed in the manifest from the cache. Generally,
+ implementors are urged to use an approach that expires
+ lesser-used resources first.</p>
</li>
@@ -57979,7 +57986,22 @@
</div>
+ <h4>Expiring application caches</h4>
+ <p>As a general rule, user agents should not expire application
+ caches, except on request from the user, or after having been left
+ unused for an extended period of time.</p>
+
+ <p>Implementors are encouraged to expose application caches in a
+ manner related to HTTP cookies, allowing caches to be expired
+ together with cookies and other origin-specific data. Application
+ caches and cookies have similar implications with respect to privacy
+ (e.g. if the site can identify the user when providing the cache, it
+ can store data in the cache that can be used for cookie
+ resurrection).</p>
+
+
+
<h4>Application cache API</h4>
<pre class="idl">interface <dfn>ApplicationCache</dfn> {
@@ -83443,6 +83465,7 @@
Allan Clements,
Anders Carlsson,
Andreas<!-- mqmq87 -->,
+ Andrei Popescu,
Andrew Clover,
Andrew Gove,
Andrew Sidwell,
More information about the Commit-Watchers
mailing list