html5/spec Overview.html,1.2342,1.2343

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv25870

Modified Files:
	Overview.html 
Log Message:
Update the appcache mechanism for handling low-storage-space cases. (whatwg r3189)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2342
retrieving revision 1.2343
diff -u -d -r1.2342 -r1.2343
--- Overview.html	4 Jun 2009 19:24:35 -0000	1.2342
+++ Overview.html	4 Jun 2009 22:29:04 -0000	1.2343
@@ -840,8 +840,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>
@@ -44970,7 +44971,15 @@
   <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>
@@ -45259,10 +45268,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>
 
@@ -45734,7 +45742,15 @@
   primed the first time), making the testing of offline applications
   simpler.</p>
 
-  </div><h4 id="application-cache-api"><span class="secno">6.9.8 </span>Application cache API</h4><pre class="idl">interface <dfn id="applicationcache">ApplicationCache</dfn> {
+  </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>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).<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>
   const unsigned short <a href="#dom-appcache-uncached" title="dom-appcache-UNCACHED">UNCACHED</a> = 0;
@@ -45930,7 +45946,7 @@
     <tr><td><dfn id="handler-appcache-onupdateready" title="handler-appcache-onupdateready"><code>onupdateready</code></dfn> <td> <code title="event-updateready">updateready</code>
     <tr><td><dfn id="handler-appcache-oncached" title="handler-appcache-oncached"><code>oncached</code></dfn> <td> <code title="event-cached">cached</code>
     <tr><td><dfn id="handler-appcache-onobsolete" title="handler-appcache-onobsolete"><code>onobsolete</code></dfn> <td> <code title="event-obsolete">obsolete</code>
-  </table></div><h4 id="browser-state"><span class="secno">6.9.9 </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>
+  </table></div><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>
 
    <dd>
 
@@ -64521,6 +64537,7 @@
   Allan Clements,
   Anders Carlsson,
   Andreas<!-- mqmq87 -->,
+  Andrei Popescu,
   Andrew Clover,
   Andrew Gove,
   Andrew Sidwell,

Received on Thursday, 4 June 2009 22:29:12 UTC