[html5] r4169 - [e] (0) Rename the 'application cache update process' to the 'application cache [...]
whatwg at whatwg.org
whatwg at whatwg.org
Sun Oct 18 04:12:27 PDT 2009
Author: ianh
Date: 2009-10-18 04:12:24 -0700 (Sun, 18 Oct 2009)
New Revision: 4169
Modified:
complete.html
index
source
Log:
[e] (0) Rename the 'application cache update process' to the 'application cache download process'
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7773
Modified: complete.html
===================================================================
--- complete.html 2009-10-18 11:06:16 UTC (rev 4168)
+++ complete.html 2009-10-18 11:12:24 UTC (rev 4169)
@@ -735,7 +735,7 @@
<li><a href=#a-sample-manifest><span class=secno>6.9.3.1 </span>A sample manifest</a></li>
<li><a href=#writing-cache-manifests><span class=secno>6.9.3.2 </span>Writing cache manifests</a></li>
<li><a href=#parsing-cache-manifests><span class=secno>6.9.3.3 </span>Parsing cache manifests</a></ol></li>
- <li><a href=#updating-an-application-cache><span class=secno>6.9.4 </span>Updating an application cache</a></li>
+ <li><a href=#downloading-or-updating-an-application-cache><span class=secno>6.9.4 </span>Downloading or updating an application cache</a></li>
<li><a href=#the-application-cache-selection-algorithm><span class=secno>6.9.5 </span>The application cache selection algorithm</a></li>
<li><a href=#changesToNetworkingModel><span class=secno>6.9.6 </span>Changes to the networking model</a></li>
<li><a href=#expiring-application-caches><span class=secno>6.9.7 </span>Expiring application caches</a></li>
@@ -52701,8 +52701,8 @@
<dd>The resource corresponding to the URL that was given in a
master entry's <code><a href=#the-html-element-0>html</a></code> element's <code title=attr-html-manifest><a href=#attr-html-manifest>manifest</a></code> attribute. The
- manifest is fetched and processed during the <a href=#application-cache-update-process>application
- cache update process</a>. All the <a href=#concept-appcache-master title=concept-appcache-master>master entries</a> have
+ manifest is fetched and processed during the <a href=#application-cache-download-process>application
+ cache download process</a>. All the <a href=#concept-appcache-master title=concept-appcache-master>master entries</a> have
the <a href=#same-origin title="same origin">same origin</a> as the manifest.
@@ -52765,7 +52765,8 @@
<p>Each <a href=#application-cache-group>application cache group</a> has a <dfn id=concept-appcache-pending-masters title=concept-appcache-pending-masters>list of pending master
entries</dfn>. Each entry in this list consists of a resource and a
corresponding <code>Document</code> object. It is used during the
- update process to ensure that new master entries are cached.</p>
+ <a href=#application-cache-download-process>application cache download process</a> to ensure that new
+ master entries are cached.</p>
<p>An <a href=#application-cache-group>application cache group</a> can be marked as <dfn id=concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</dfn>, meaning that it
must be ignored when looking at what <a href=#application-cache-group title="application cache
@@ -53326,10 +53327,10 @@
</div>
- <h4 id=updating-an-application-cache><span class=secno>6.9.4 </span>Updating an application cache</h4>
+ <h4 id=downloading-or-updating-an-application-cache><span class=secno>6.9.4 </span>Downloading or updating an application cache</h4>
<p>When the user agent is required (by other parts of this
- specification) to start the <dfn id=application-cache-update-process>application cache update
+ specification) to start the <dfn id=application-cache-download-process>application cache download
process</dfn> for an <a href=#absolute-url>absolute URL</a> purported to identify
a <a href=#concept-appcache-manifest title=concept-appcache-manifest>manifest</a>, or for an
<a href=#application-cache-group>application cache group</a>, potentially given a particular
@@ -53340,8 +53341,8 @@
agent <dfn id=shows-caching-progress>shows caching progress</dfn>. Support for this is
optional. Caching progress UI could consist of a progress bar or
message panel in the user agent's interface, or an overlay, or
- something else. Certain events fired during the <a href=#application-cache-update-process>application
- cache update process</a> allow the script to override the display
+ something else. Certain events fired during the <a href=#application-cache-download-process>application
+ cache download process</a> allow the script to override the display
of such an interface. The goal of this is to allow Web applications
to provide more seamless update mechanisms, hiding from the user the
mechanics of the application cache mechanism. User agents may
@@ -53349,17 +53350,17 @@
not show prominent update progress notifications for applications
that cancel the relevant events.</p>
- <p>The <a href=#application-cache-update-process>application cache update process</a> steps are as
+ <p>The <a href=#application-cache-download-process>application cache download process</a> steps are as
follows:
- <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. The
- algorithm might never get past this point. (This step is
- particularly intended to be used by user agents running on severely
- space-constrained devices or in highly privacy-sensitive
- environments).</li>
+ <ol><li><p>Optionally, wait until the permission to start the
+ <a href=#application-cache-download-process>application cache download process</a> 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. The algorithm might never get past this
+ point. (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>
@@ -53431,8 +53432,9 @@
<li><p>If the <a href=#concept-appcache-status title=concept-appcache-status>status</a>
of the <var title="">cache group</var> is either <i>checking</i>
- or <i>downloading</i>, then abort this instance of the update
- process, as an update is already in progress for them.</li>
+ or <i>downloading</i>, then abort this instance of the
+ <a href=#application-cache-download-process>application cache download process</a>, as an update is
+ already in progress.</li>
<li><p>Set the <a href=#concept-appcache-status title=concept-appcache-status>status</a> of <var title="">cache group</var> to <i>checking</i>.</p>
@@ -53525,7 +53527,8 @@
<li><p>Let the <a href=#concept-appcache-status title=concept-appcache-status>status</a> of <var title="">cache group</var> be <i>idle</i>.</li>
- <li><p>Abort the update process.</li>
+ <li><p>Abort the <a href=#application-cache-download-process>application cache download
+ process</a>.</li>
</ol></li>
@@ -53579,7 +53582,7 @@
(application caches never include fragment identifiers).</p>
<p class=note>HTTP caching rules, such as <code title="">Cache-Control: no-store</code>, are ignored for the
- purposes of the <a href=#application-cache-update-process>application cache update
+ purposes of the <a href=#application-cache-download-process>application cache download
process</a>.</p>
</li>
@@ -53602,7 +53605,8 @@
<li><p>Let the <a href=#concept-appcache-status title=concept-appcache-status>status</a> of <var title="">cache group</var> be <i>idle</i>.</li>
- <li><p>Abort the update process.</li>
+ <li><p>Abort the <a href=#application-cache-download-process>application cache download
+ process</a>.</li>
</ol></li>
@@ -53854,7 +53858,8 @@
<li><p>If appropriate, remove any user interface indicating
that an update for this cache is in progress.</li>
- <li><p>Abort the update process.</li>
+ <li><p>Abort the <a href=#application-cache-download-process>application cache download
+ process</a>.</li>
</ol></li>
@@ -53985,14 +53990,15 @@
attempt</a>, discard <var title="">cache group</var>
altogether.</p>
- <li><p>Abort the update process.</li>
+ <li><p>Abort the <a href=#application-cache-download-process>application cache download
+ process</a>.</li>
</ol><p>Attempts to <a href=#fetch>fetch</a> resources as part of the
- <a href=#application-cache-update-process>application cache update process</a> may be done with
+ <a href=#application-cache-download-process>application cache download process</a> may be done with
cache-defeating semantics, to avoid problems with stale or
inconsistent intermediary caches.</p>
- <hr><p>User agents may invoke the <a href=#application-cache-update-process>application cache update
+ <hr><p>User agents may invoke the <a href=#application-cache-download-process>application cache download
process</a>, in the background, for any <a href=#application-cache>application
cache</a>, at any time (with no <a href=#cache-host>cache host</a>). This
allows user agents to keep caches primed and to update caches even
@@ -54049,7 +54055,7 @@
<p>Associate <var title="">document</var> with the
<a href=#application-cache>application cache</a> from which it was loaded. Invoke
- the <a href=#application-cache-update-process>application cache update process</a> for that
+ the <a href=#application-cache-download-process>application cache download process</a> for that
<a href=#application-cache>application cache</a>'s <a href=#application-cache-group>application cache
group</a>, with <var title="">document</var> as the <a href=#cache-host>cache
host</a>.</p>
@@ -54066,7 +54072,7 @@
<dd>
- <p>Invoke the <a href=#application-cache-update-process>application cache update process</a> for
+ <p>Invoke the <a href=#application-cache-download-process>application cache download process</a> for
<var title="">manifest URL</var>, with <var title="">document</var> as the <a href=#cache-host>cache host</a> and with
the resource from which <var title="">document</var> was parsed as
the new <a href=#concept-appcache-master title=concept-appcache-master>master</a>
@@ -54223,7 +54229,7 @@
<dt><var title="">cache</var> . <code title=dom-appcache-update><a href=#dom-appcache-update>update</a></code>()</dt>
<dd>
- <p>Invokes the application cache update process.</p>
+ <p>Invokes the <a href=#application-cache-download-process>application cache download process</a>.</p>
<p>Throws an <code><a href=#invalid_state_err>INVALID_STATE_ERR</a></code> exception if there is no application cache to update.</p>
@@ -54323,8 +54329,8 @@
</dl><div class=impl>
<hr><p>If the <dfn id=dom-appcache-update title=dom-appcache-update><code>update()</code></dfn> method is
- invoked, the user agent must invoke the <a href=#application-cache-update-process>application cache
- update process</a>, in the background, for the <a href=#application-cache>application
+ invoked, the user agent must invoke the <a href=#application-cache-download-process>application cache
+ download process</a>, in the background, for the <a href=#application-cache>application
cache</a> with which the <code><a href=#applicationcache>ApplicationCache</a></code> object's
<a href=#cache-host>cache host</a> is associated, but without giving that
<a href=#cache-host>cache host</a> to the algorithm. If there is no such
Modified: index
===================================================================
--- index 2009-10-18 11:06:16 UTC (rev 4168)
+++ index 2009-10-18 11:12:24 UTC (rev 4169)
@@ -711,7 +711,7 @@
<li><a href=#a-sample-manifest><span class=secno>6.9.3.1 </span>A sample manifest</a></li>
<li><a href=#writing-cache-manifests><span class=secno>6.9.3.2 </span>Writing cache manifests</a></li>
<li><a href=#parsing-cache-manifests><span class=secno>6.9.3.3 </span>Parsing cache manifests</a></ol></li>
- <li><a href=#updating-an-application-cache><span class=secno>6.9.4 </span>Updating an application cache</a></li>
+ <li><a href=#downloading-or-updating-an-application-cache><span class=secno>6.9.4 </span>Downloading or updating an application cache</a></li>
<li><a href=#the-application-cache-selection-algorithm><span class=secno>6.9.5 </span>The application cache selection algorithm</a></li>
<li><a href=#changesToNetworkingModel><span class=secno>6.9.6 </span>Changes to the networking model</a></li>
<li><a href=#expiring-application-caches><span class=secno>6.9.7 </span>Expiring application caches</a></li>
@@ -49860,8 +49860,8 @@
<dd>The resource corresponding to the URL that was given in a
master entry's <code><a href=#the-html-element-0>html</a></code> element's <code title=attr-html-manifest><a href=#attr-html-manifest>manifest</a></code> attribute. The
- manifest is fetched and processed during the <a href=#application-cache-update-process>application
- cache update process</a>. All the <a href=#concept-appcache-master title=concept-appcache-master>master entries</a> have
+ manifest is fetched and processed during the <a href=#application-cache-download-process>application
+ cache download process</a>. All the <a href=#concept-appcache-master title=concept-appcache-master>master entries</a> have
the <a href=#same-origin title="same origin">same origin</a> as the manifest.
@@ -49924,7 +49924,8 @@
<p>Each <a href=#application-cache-group>application cache group</a> has a <dfn id=concept-appcache-pending-masters title=concept-appcache-pending-masters>list of pending master
entries</dfn>. Each entry in this list consists of a resource and a
corresponding <code>Document</code> object. It is used during the
- update process to ensure that new master entries are cached.</p>
+ <a href=#application-cache-download-process>application cache download process</a> to ensure that new
+ master entries are cached.</p>
<p>An <a href=#application-cache-group>application cache group</a> can be marked as <dfn id=concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</dfn>, meaning that it
must be ignored when looking at what <a href=#application-cache-group title="application cache
@@ -50485,10 +50486,10 @@
</div>
- <h4 id=updating-an-application-cache><span class=secno>6.9.4 </span>Updating an application cache</h4>
+ <h4 id=downloading-or-updating-an-application-cache><span class=secno>6.9.4 </span>Downloading or updating an application cache</h4>
<p>When the user agent is required (by other parts of this
- specification) to start the <dfn id=application-cache-update-process>application cache update
+ specification) to start the <dfn id=application-cache-download-process>application cache download
process</dfn> for an <a href=#absolute-url>absolute URL</a> purported to identify
a <a href=#concept-appcache-manifest title=concept-appcache-manifest>manifest</a>, or for an
<a href=#application-cache-group>application cache group</a>, potentially given a particular
@@ -50499,8 +50500,8 @@
agent <dfn id=shows-caching-progress>shows caching progress</dfn>. Support for this is
optional. Caching progress UI could consist of a progress bar or
message panel in the user agent's interface, or an overlay, or
- something else. Certain events fired during the <a href=#application-cache-update-process>application
- cache update process</a> allow the script to override the display
+ something else. Certain events fired during the <a href=#application-cache-download-process>application
+ cache download process</a> allow the script to override the display
of such an interface. The goal of this is to allow Web applications
to provide more seamless update mechanisms, hiding from the user the
mechanics of the application cache mechanism. User agents may
@@ -50508,17 +50509,17 @@
not show prominent update progress notifications for applications
that cancel the relevant events.</p>
- <p>The <a href=#application-cache-update-process>application cache update process</a> steps are as
+ <p>The <a href=#application-cache-download-process>application cache download process</a> steps are as
follows:
- <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. The
- algorithm might never get past this point. (This step is
- particularly intended to be used by user agents running on severely
- space-constrained devices or in highly privacy-sensitive
- environments).</li>
+ <ol><li><p>Optionally, wait until the permission to start the
+ <a href=#application-cache-download-process>application cache download process</a> 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. The algorithm might never get past this
+ point. (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>
@@ -50590,8 +50591,9 @@
<li><p>If the <a href=#concept-appcache-status title=concept-appcache-status>status</a>
of the <var title="">cache group</var> is either <i>checking</i>
- or <i>downloading</i>, then abort this instance of the update
- process, as an update is already in progress for them.</li>
+ or <i>downloading</i>, then abort this instance of the
+ <a href=#application-cache-download-process>application cache download process</a>, as an update is
+ already in progress.</li>
<li><p>Set the <a href=#concept-appcache-status title=concept-appcache-status>status</a> of <var title="">cache group</var> to <i>checking</i>.</p>
@@ -50684,7 +50686,8 @@
<li><p>Let the <a href=#concept-appcache-status title=concept-appcache-status>status</a> of <var title="">cache group</var> be <i>idle</i>.</li>
- <li><p>Abort the update process.</li>
+ <li><p>Abort the <a href=#application-cache-download-process>application cache download
+ process</a>.</li>
</ol></li>
@@ -50738,7 +50741,7 @@
(application caches never include fragment identifiers).</p>
<p class=note>HTTP caching rules, such as <code title="">Cache-Control: no-store</code>, are ignored for the
- purposes of the <a href=#application-cache-update-process>application cache update
+ purposes of the <a href=#application-cache-download-process>application cache download
process</a>.</p>
</li>
@@ -50761,7 +50764,8 @@
<li><p>Let the <a href=#concept-appcache-status title=concept-appcache-status>status</a> of <var title="">cache group</var> be <i>idle</i>.</li>
- <li><p>Abort the update process.</li>
+ <li><p>Abort the <a href=#application-cache-download-process>application cache download
+ process</a>.</li>
</ol></li>
@@ -51013,7 +51017,8 @@
<li><p>If appropriate, remove any user interface indicating
that an update for this cache is in progress.</li>
- <li><p>Abort the update process.</li>
+ <li><p>Abort the <a href=#application-cache-download-process>application cache download
+ process</a>.</li>
</ol></li>
@@ -51144,14 +51149,15 @@
attempt</a>, discard <var title="">cache group</var>
altogether.</p>
- <li><p>Abort the update process.</li>
+ <li><p>Abort the <a href=#application-cache-download-process>application cache download
+ process</a>.</li>
</ol><p>Attempts to <a href=#fetch>fetch</a> resources as part of the
- <a href=#application-cache-update-process>application cache update process</a> may be done with
+ <a href=#application-cache-download-process>application cache download process</a> may be done with
cache-defeating semantics, to avoid problems with stale or
inconsistent intermediary caches.</p>
- <hr><p>User agents may invoke the <a href=#application-cache-update-process>application cache update
+ <hr><p>User agents may invoke the <a href=#application-cache-download-process>application cache download
process</a>, in the background, for any <a href=#application-cache>application
cache</a>, at any time (with no <a href=#cache-host>cache host</a>). This
allows user agents to keep caches primed and to update caches even
@@ -51208,7 +51214,7 @@
<p>Associate <var title="">document</var> with the
<a href=#application-cache>application cache</a> from which it was loaded. Invoke
- the <a href=#application-cache-update-process>application cache update process</a> for that
+ the <a href=#application-cache-download-process>application cache download process</a> for that
<a href=#application-cache>application cache</a>'s <a href=#application-cache-group>application cache
group</a>, with <var title="">document</var> as the <a href=#cache-host>cache
host</a>.</p>
@@ -51225,7 +51231,7 @@
<dd>
- <p>Invoke the <a href=#application-cache-update-process>application cache update process</a> for
+ <p>Invoke the <a href=#application-cache-download-process>application cache download process</a> for
<var title="">manifest URL</var>, with <var title="">document</var> as the <a href=#cache-host>cache host</a> and with
the resource from which <var title="">document</var> was parsed as
the new <a href=#concept-appcache-master title=concept-appcache-master>master</a>
@@ -51382,7 +51388,7 @@
<dt><var title="">cache</var> . <code title=dom-appcache-update><a href=#dom-appcache-update>update</a></code>()</dt>
<dd>
- <p>Invokes the application cache update process.</p>
+ <p>Invokes the <a href=#application-cache-download-process>application cache download process</a>.</p>
<p>Throws an <code><a href=#invalid_state_err>INVALID_STATE_ERR</a></code> exception if there is no application cache to update.</p>
@@ -51482,8 +51488,8 @@
</dl><div class=impl>
<hr><p>If the <dfn id=dom-appcache-update title=dom-appcache-update><code>update()</code></dfn> method is
- invoked, the user agent must invoke the <a href=#application-cache-update-process>application cache
- update process</a>, in the background, for the <a href=#application-cache>application
+ invoked, the user agent must invoke the <a href=#application-cache-download-process>application cache
+ download process</a>, in the background, for the <a href=#application-cache>application
cache</a> with which the <code><a href=#applicationcache>ApplicationCache</a></code> object's
<a href=#cache-host>cache host</a> is associated, but without giving that
<a href=#cache-host>cache host</a> to the algorithm. If there is no such
Modified: source
===================================================================
--- source 2009-10-18 11:06:16 UTC (rev 4168)
+++ source 2009-10-18 11:12:24 UTC (rev 4169)
@@ -59334,7 +59334,7 @@
master entry's <code>html</code> element's <code
title="attr-html-manifest">manifest</code> attribute. The
manifest is fetched and processed during the <span>application
- cache update process</span>. All the <span
+ cache download process</span>. All the <span
title="concept-appcache-master">master entries</span> have
the <span title="same origin">same origin</span> as the manifest.
@@ -59425,7 +59425,8 @@
title="concept-appcache-pending-masters">list of pending master
entries</dfn>. Each entry in this list consists of a resource and a
corresponding <code>Document</code> object. It is used during the
- update process to ensure that new master entries are cached.</p>
+ <span>application cache download process</span> to ensure that new
+ master entries are cached.</p>
<p>An <span>application cache group</span> can be marked as <dfn
title="concept-appcache-obsolete">obsolete</dfn>, meaning that it
@@ -60076,10 +60077,10 @@
</div>
- <h4>Updating an application cache</h4>
+ <h4>Downloading or updating an application cache</h4>
<p>When the user agent is required (by other parts of this
- specification) to start the <dfn>application cache update
+ specification) to start the <dfn>application cache download
process</dfn> for an <span>absolute URL</span> purported to identify
a <span title="concept-appcache-manifest">manifest</span>, or for an
<span>application cache group</span>, potentially given a particular
@@ -60092,7 +60093,7 @@
optional. Caching progress UI could consist of a progress bar or
message panel in the user agent's interface, or an overlay, or
something else. Certain events fired during the <span>application
- cache update process</span> allow the script to override the display
+ cache download process</span> allow the script to override the display
of such an interface. The goal of this is to allow Web applications
to provide more seamless update mechanisms, hiding from the user the
mechanics of the application cache mechanism. User agents may
@@ -60100,19 +60101,19 @@
not show prominent update progress notifications for applications
that cancel the relevant events.</p>
- <p>The <span>application cache update process</span> steps are as
+ <p>The <span>application cache download process</span> steps are as
follows:
<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. The
- algorithm might never get past this point. (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>Optionally, wait until the permission to start the
+ <span>application cache download process</span> 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. The algorithm might never get past this
+ point. (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>
@@ -60203,8 +60204,9 @@
<li><p>If the <span title="concept-appcache-status">status</span>
of the <var title="">cache group</var> is either <i>checking</i>
- or <i>downloading</i>, then abort this instance of the update
- process, as an update is already in progress for them.</p></li>
+ or <i>downloading</i>, then abort this instance of the
+ <span>application cache download process</span>, as an update is
+ already in progress.</p></li>
<li><p>Set the <span
title="concept-appcache-status">status</span> of <var
@@ -60320,7 +60322,8 @@
title="concept-appcache-status">status</span> of <var
title="">cache group</var> be <i>idle</i>.</p></li>
- <li><p>Abort the update process.</p></li>
+ <li><p>Abort the <span>application cache download
+ process</span>.</p></li>
</ol>
@@ -60387,7 +60390,7 @@
<p class="note">HTTP caching rules, such as <code
title="">Cache-Control: no-store</code>, are ignored for the
- purposes of the <span>application cache update
+ purposes of the <span>application cache download
process</span>.</p>
</li>
@@ -60414,7 +60417,8 @@
title="concept-appcache-status">status</span> of <var
title="">cache group</var> be <i>idle</i>.</p></li>
- <li><p>Abort the update process.</p></li>
+ <li><p>Abort the <span>application cache download
+ process</span>.</p></li>
</ol>
@@ -60708,7 +60712,8 @@
<li><p>If appropriate, remove any user interface indicating
that an update for this cache is in progress.</p></li>
- <li><p>Abort the update process.</p></li>
+ <li><p>Abort the <span>application cache download
+ process</span>.</p></li>
</ol>
@@ -60863,18 +60868,19 @@
attempt</span>, discard <var title="">cache group</var>
altogether.</p>
- <li><p>Abort the update process.</p></li>
+ <li><p>Abort the <span>application cache download
+ process</span>.</p></li>
</ol>
<p>Attempts to <span>fetch</span> resources as part of the
- <span>application cache update process</span> may be done with
+ <span>application cache download process</span> may be done with
cache-defeating semantics, to avoid problems with stale or
inconsistent intermediary caches.</p>
<hr>
- <p>User agents may invoke the <span>application cache update
+ <p>User agents may invoke the <span>application cache download
process</span>, in the background, for any <span>application
cache</span>, at any time (with no <span>cache host</span>). This
allows user agents to keep caches primed and to update caches even
@@ -60938,7 +60944,7 @@
<p>Associate <var title="">document</var> with the
<span>application cache</span> from which it was loaded. Invoke
- the <span>application cache update process</span> for that
+ the <span>application cache download process</span> for that
<span>application cache</span>'s <span>application cache
group</span>, with <var title="">document</var> as the <span>cache
host</span>.</p>
@@ -60955,7 +60961,7 @@
<dd>
- <p>Invoke the <span>application cache update process</span> for
+ <p>Invoke the <span>application cache download process</span> for
<var title="">manifest URL</var>, with <var
title="">document</var> as the <span>cache host</span> and with
the resource from which <var title="">document</var> was parsed as
@@ -61132,7 +61138,7 @@
<dt><var title="">cache</var> . <code title="dom-appcache-update">update</code>()</dt>
<dd>
- <p>Invokes the application cache update process.</p>
+ <p>Invokes the <span>application cache download process</span>.</p>
<p>Throws an <code>INVALID_STATE_ERR</code> exception if there is no application cache to update.</p>
@@ -61254,7 +61260,7 @@
<p>If the <dfn
title="dom-appcache-update"><code>update()</code></dfn> method is
invoked, the user agent must invoke the <span>application cache
- update process</span>, in the background, for the <span>application
+ download process</span>, in the background, for the <span>application
cache</span> with which the <code>ApplicationCache</code> object's
<span>cache host</span> is associated, but without giving that
<span>cache host</span> to the algorithm. If there is no such
More information about the Commit-Watchers
mailing list