[] (0) Update the appcache mechanism for handling low-storage-space c…

…ases. git-svn-id: http://svn.whatwg.org/webapps@3189 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Jun 4, 2009 · ac258e0 · ac258e0
1 parent 9076fea
commit ac258e0
Show file tree

Hide file tree

Showing 2 changed files with 60 additions and 13 deletions.
diff --git a/index b/index
@@ -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,7 +50020,15 @@ style/default.css</pre>
   <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 @@ style/default.css</pre>
       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,8 +50794,23 @@ style/default.css</pre>
   </div>
 
 
+  <h4 id=expiring-application-caches><span class=secno>6.9.8 </span>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 id=application-cache-api><span class=secno>6.9.8 </span>Application cache API</h4>
+  <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> {
 
@@ -50992,7 +51015,7 @@ style/default.css</pre>
   </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 @@ S SPACER STRIKE TT U -->
   Allan Clements,
   Anders Carlsson,
   Andreas<!-- mqmq87 -->,
+  Andrei Popescu,
   Andrew Clover,
   Andrew Gove,
   Andrew Sidwell,

diff --git a/source b/source
@@ -57067,6 +57067,14 @@ style/default.css</pre>
 
   <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 @@ style/default.css</pre>
       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,6 +57986,21 @@ style/default.css</pre>
   </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>
 
@@ -83443,6 +83465,7 @@ S SPACER STRIKE TT U -->
   Allan Clements,
   Anders Carlsson,
   Andreas<!-- mqmq87 -->,
+  Andrei Popescu,
   Andrew Clover,
   Andrew Gove,
   Andrew Sidwell,