- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 25 Sep 2010 18:12:28 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv23167
Modified Files:
Overview.html
Log Message:
Add an example of absolute URLs in appcaches. (whatwg r5492)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4382
retrieving revision 1.4383
diff -u -d -r1.4382 -r1.4383
--- Overview.html 25 Sep 2010 18:05:36 -0000 1.4382
+++ Overview.html 25 Sep 2010 18:12:24 -0000 1.4383
@@ -958,7 +958,7 @@
<li><a href="#appcache"><span class="secno">5.6.2 </span>Application caches</a></li>
<li><a href="#manifests"><span class="secno">5.6.3 </span>The cache manifest syntax</a>
<ol>
- <li><a href="#a-sample-manifest"><span class="secno">5.6.3.1 </span>A sample manifest</a></li>
+ <li><a href="#some-sample-manifests"><span class="secno">5.6.3.1 </span>Some sample manifests</a></li>
<li><a href="#writing-cache-manifests"><span class="secno">5.6.3.2 </span>Writing cache manifests</a></li>
<li><a href="#parsing-cache-manifests"><span class="secno">5.6.3.3 </span>Parsing cache manifests</a></ol></li>
<li><a href="#downloading-or-updating-an-application-cache"><span class="secno">5.6.4 </span>Downloading or updating an application cache</a></li>
@@ -45187,8 +45187,12 @@
</div>
- </div><h4 id="manifests"><span class="secno">5.6.3 </span>The cache manifest syntax</h4><h5 id="a-sample-manifest"><span class="secno">5.6.3.1 </span>A sample manifest</h5><p><i>This section is non-normative.</i><p>This example manifest requires two images and a style sheet to be
- cached and whitelists a CGI script.<pre>CACHE MANIFEST
+ </div><h4 id="manifests"><span class="secno">5.6.3 </span>The cache manifest syntax</h4><h5 id="some-sample-manifests"><span class="secno">5.6.3.1 </span>Some sample manifests</h5><p><i>This section is non-normative.</i><div class="example">
+
+ <p>This example manifest requires two images and a style sheet to be
+ cached and whitelists a CGI script.</p>
+
+ <pre>CACHE MANIFEST
# the above line is required
# this is a comment
@@ -45214,29 +45218,60 @@
# here is another set of files to cache, this time just the CSS file.
CACHE:
-style/default.css</pre><p>It could equally well be written as follows:<pre>CACHE MANIFEST
+style/default.css</pre>
+
+ <p>It could equally well be written as follows:</p>
+
+ <pre>CACHE MANIFEST
NETWORK:
comm.cgi
CACHE:
style/default.css
images/sound-icon.png
-images/background.png</pre><hr><p>The following manifest defines a catch-all error page that is
- displayed for any page on the site while the user is offline. It
- also specifies that the <a href="#concept-appcache-onlinewhitelist-wildcard" title="concept-appcache-onlinewhitelist-wildcard">online whitelist
- wildcard flag</a> is <i title="">open</i>, meaning that accesses
- to resources on other sites will not be blocked. (Resources on the
- same site are already not blocked because of the catch-all fallback
- namespace.)<p>So long as all pages on the site reference this manifest, they
- will get cached locally as they are fetched, so that subsequent hits
- to the same page will load the page immediately from the
- cache. Until the manifest is changed, those pages will not be
- fetched from the server again. When the manifest changes, then all
- the files will be redownloaded.<p>Subresources, such as style sheets, images, etc, would only be
- cached using the regular HTTP caching semantics, however.<pre>CACHE MANIFEST
+images/background.png</pre>
+
+ </div><div class="example">
+
+ <p>Offline application cache manifests can use absolute paths or
+ even absolute URLs:</p>
+
+ <pre>CACHE MANIFEST
+
+/main/home
+/main/app.js
+/settings/home
+/settings/app.js
+http://img.example.com/logo.png
+http://img.example.com/check.png
+http://img.example.com/cross.png</pre>
+
+ </div><div class="example">
+
+ <p>The following manifest defines a catch-all error page that is
+ displayed for any page on the site while the user is offline. It
+ also specifies that the <a href="#concept-appcache-onlinewhitelist-wildcard" title="concept-appcache-onlinewhitelist-wildcard">online whitelist
+ wildcard flag</a> is <i title="">open</i>, meaning that accesses
+ to resources on other sites will not be blocked. (Resources on the
+ same site are already not blocked because of the catch-all fallback
+ namespace.)</p>
+
+ <p>So long as all pages on the site reference this manifest, they
+ will get cached locally as they are fetched, so that subsequent hits
+ to the same page will load the page immediately from the
+ cache. Until the manifest is changed, those pages will not be
+ fetched from the server again. When the manifest changes, then all
+ the files will be redownloaded.</p>
+
+ <p>Subresources, such as style sheets, images, etc, would only be
+ cached using the regular HTTP caching semantics, however.</p>
+
+ <pre>CACHE MANIFEST
FALLBACK:
/ /offline.html
NETWORK:
-*</pre><h5 id="writing-cache-manifests"><span class="secno">5.6.3.2 </span>Writing cache manifests</h5><p>Manifests must be served using the
+*</pre>
+
+ </div><h5 id="writing-cache-manifests"><span class="secno">5.6.3.2 </span>Writing cache manifests</h5><p>Manifests must be served using the
<code><a href="#text-cache-manifest">text/cache-manifest</a></code> <a href="#mime-type">MIME type</a>. All
resources served using the <code><a href="#text-cache-manifest">text/cache-manifest</a></code>
<a href="#mime-type">MIME type</a> must follow the syntax of application cache
Received on Saturday, 25 September 2010 18:12:32 UTC