[html5] r5287 - [giow] (1) disk space limitations for appcache

whatwg at whatwg.org whatwg at whatwg.org
Thu Aug 12 15:28:40 PDT 2010


Author: ianh
Date: 2010-08-12 15:28:39 -0700 (Thu, 12 Aug 2010)
New Revision: 5287

Modified:
   complete.html
   index
   source
Log:
[giow] (1) disk space limitations for appcache

Modified: complete.html
===================================================================
--- complete.html	2010-08-12 20:32:38 UTC (rev 5286)
+++ complete.html	2010-08-12 22:28:39 UTC (rev 5287)
@@ -888,8 +888,9 @@
      <li><a href=#the-application-cache-selection-algorithm><span class=secno>6.6.5 </span>The application cache selection algorithm</a></li>
      <li><a href=#changesToNetworkingModel><span class=secno>6.6.6 </span>Changes to the networking model</a></li>
      <li><a href=#expiring-application-caches><span class=secno>6.6.7 </span>Expiring application caches</a></li>
-     <li><a href=#application-cache-api><span class=secno>6.6.8 </span>Application cache API</a></li>
-     <li><a href=#browser-state><span class=secno>6.6.9 </span>Browser state</a></ol></ol></li>
+     <li><a href=#disk-space><span class=secno>6.6.8 </span>Disk space</a></li>
+     <li><a href=#application-cache-api><span class=secno>6.6.9 </span>Application cache API</a></li>
+     <li><a href=#browser-state><span class=secno>6.6.10 </span>Browser state</a></ol></ol></li>
  <li><a href=#webappapis><span class=secno>7 </span>Web application APIs</a>
   <ol>
    <li><a href=#scripting><span class=secno>7.1 </span>Scripting</a>
@@ -1117,7 +1118,7 @@
       <ol>
        <li><a href=#event-definition-0><span class=secno>11.2.4.1 </span>Event definition</a></ol></li>
      <li><a href=#threads><span class=secno>11.2.5 </span>Threads</a></ol></li>
-   <li><a href=#disk-space><span class=secno>11.3 </span>Disk space</a></li>
+   <li><a href=#disk-space-0><span class=secno>11.3 </span>Disk space</a></li>
    <li><a href=#privacy><span class=secno>11.4 </span>Privacy</a>
     <ol>
      <li><a href=#user-tracking><span class=secno>11.4.1 </span>User tracking</a></li>
@@ -62640,9 +62641,20 @@
 
      </li>
 
-     <li><p>Otherwise, the fetching succeeded. Store the resource in
-     the <var title="">new cache</var>.</li>
+     <li>
 
+      <p>Otherwise, the fetching succeeded. Store the resource in
+      the <var title="">new cache</var>.</p>
+
+      <p>If the user agent is not able to store the resource (e.g.
+      because of quota restrictions), the user agent may prompt the
+      user or try to resolve the problem in some other manner (e.g.
+      automatically pruning content in other caches). If the problem
+      cannot be resolved, the user agent must run the <a href=#cache-failure-steps>cache
+      failure steps</a>.</p>
+
+     </li>
+
      <li><p>If the URL being processed was flagged as an "explicit
      entry" in <var title="">file list</var>, then categorize the
      entry as an <a href=#concept-appcache-explicit title=concept-appcache-explicit>explicit
@@ -63085,9 +63097,20 @@
   once.</p>
 
 
+  <h4 id=disk-space><span class=secno>6.6.8 </span>Disk space</h4>
 
-  <h4 id=application-cache-api><span class=secno>6.6.8 </span>Application cache API</h4>
+  <p>User agents should consider applying constraints on disk usage of
+  <a href=#application-cache title="application cache">application caches</a>, and care
+  should be taken to ensure that the restrictions cannot be easily
+  worked around using subdomains.</p>
 
+  <p>User agents should allow users to see how much space each domain
+  is using, and may offer the user the ability to delete specific
+  <a href=#application-cache title="application cache">application caches</a>.</p>
+
+
+  <h4 id=application-cache-api><span class=secno>6.6.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>
@@ -63303,7 +63326,7 @@
   </table></div>
 
 
-  <h4 id=browser-state><span class=secno>6.6.9 </span>Browser state</h4>
+  <h4 id=browser-state><span class=secno>6.6.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>
 
@@ -77002,7 +77025,7 @@
   
   
 
-  <h3 id=disk-space><span class=secno>11.3 </span>Disk space</h3>
+  <h3 id=disk-space-0><span class=secno>11.3 </span>Disk space</h3>
 
   <p>User agents should limit the total amount of space allowed for
   

Modified: index
===================================================================
--- index	2010-08-12 20:32:38 UTC (rev 5286)
+++ index	2010-08-12 22:28:39 UTC (rev 5287)
@@ -895,8 +895,9 @@
      <li><a href=#the-application-cache-selection-algorithm><span class=secno>6.6.5 </span>The application cache selection algorithm</a></li>
      <li><a href=#changesToNetworkingModel><span class=secno>6.6.6 </span>Changes to the networking model</a></li>
      <li><a href=#expiring-application-caches><span class=secno>6.6.7 </span>Expiring application caches</a></li>
-     <li><a href=#application-cache-api><span class=secno>6.6.8 </span>Application cache API</a></li>
-     <li><a href=#browser-state><span class=secno>6.6.9 </span>Browser state</a></ol></ol></li>
+     <li><a href=#disk-space><span class=secno>6.6.8 </span>Disk space</a></li>
+     <li><a href=#application-cache-api><span class=secno>6.6.9 </span>Application cache API</a></li>
+     <li><a href=#browser-state><span class=secno>6.6.10 </span>Browser state</a></ol></ol></li>
  <li><a href=#webappapis><span class=secno>7 </span>Web application APIs</a>
   <ol>
    <li><a href=#scripting><span class=secno>7.1 </span>Scripting</a>
@@ -62576,9 +62577,20 @@
 
      </li>
 
-     <li><p>Otherwise, the fetching succeeded. Store the resource in
-     the <var title="">new cache</var>.</li>
+     <li>
 
+      <p>Otherwise, the fetching succeeded. Store the resource in
+      the <var title="">new cache</var>.</p>
+
+      <p>If the user agent is not able to store the resource (e.g.
+      because of quota restrictions), the user agent may prompt the
+      user or try to resolve the problem in some other manner (e.g.
+      automatically pruning content in other caches). If the problem
+      cannot be resolved, the user agent must run the <a href=#cache-failure-steps>cache
+      failure steps</a>.</p>
+
+     </li>
+
      <li><p>If the URL being processed was flagged as an "explicit
      entry" in <var title="">file list</var>, then categorize the
      entry as an <a href=#concept-appcache-explicit title=concept-appcache-explicit>explicit
@@ -63021,9 +63033,20 @@
   once.</p>
 
 
+  <h4 id=disk-space><span class=secno>6.6.8 </span>Disk space</h4>
 
-  <h4 id=application-cache-api><span class=secno>6.6.8 </span>Application cache API</h4>
+  <p>User agents should consider applying constraints on disk usage of
+  <a href=#application-cache title="application cache">application caches</a>, and care
+  should be taken to ensure that the restrictions cannot be easily
+  worked around using subdomains.</p>
 
+  <p>User agents should allow users to see how much space each domain
+  is using, and may offer the user the ability to delete specific
+  <a href=#application-cache title="application cache">application caches</a>.</p>
+
+
+  <h4 id=application-cache-api><span class=secno>6.6.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>
@@ -63245,7 +63268,7 @@
   </table></div>
 
 
-  <h4 id=browser-state><span class=secno>6.6.9 </span>Browser state</h4>
+  <h4 id=browser-state><span class=secno>6.6.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>
 

Modified: source
===================================================================
--- source	2010-08-12 20:32:38 UTC (rev 5286)
+++ source	2010-08-12 22:28:39 UTC (rev 5287)
@@ -70829,9 +70829,20 @@
 
      </li>
 
-     <li><p>Otherwise, the fetching succeeded. Store the resource in
-     the <var title="">new cache</var>.</p></li>
+     <li>
 
+      <p>Otherwise, the fetching succeeded. Store the resource in
+      the <var title="">new cache</var>.</p>
+
+      <p>If the user agent is not able to store the resource (e.g.
+      because of quota restrictions), the user agent may prompt the
+      user or try to resolve the problem in some other manner (e.g.
+      automatically pruning content in other caches). If the problem
+      cannot be resolved, the user agent must run the <span>cache
+      failure steps</span>.</p>
+
+     </li>
+
      <li><p>If the URL being processed was flagged as an "explicit
      entry" in <var title="">file list</var>, then categorize the
      entry as an <span title="concept-appcache-explicit">explicit
@@ -71365,7 +71376,18 @@
   once.</p>
 
 
+  <h4>Disk space</h4>
 
+  <p>User agents should consider applying constraints on disk usage of
+  <span title="application cache">application caches</span>, and care
+  should be taken to ensure that the restrictions cannot be easily
+  worked around using subdomains.</p>
+
+  <p>User agents should allow users to see how much space each domain
+  is using, and may offer the user the ability to delete specific
+  <span title="application cache">application caches</span>.</p>
+
+
   <h4>Application cache API</h4>
 
   <pre class="idl">interface <dfn>ApplicationCache</dfn> {




More information about the Commit-Watchers mailing list