- From: poot <cvsmail@w3.org>
- Date: Tue, 12 Aug 2008 08:29:22 +0900 (JST)
- To: public-html-diffs@w3.org
A sample application cache manifest. (whatwg r2048) 5.7.3.3. Parsing cache manifests http://people.w3.org/mike/diffs/html5/spec/Overview.1.1233.html#parsing1 5.7.3.1. A sample manifest http://people.w3.org/mike/diffs/html5/spec/Overview.1.1233.html#a-sample 5.7.3.2. Writing cache manifests http://people.w3.org/mike/diffs/html5/spec/Overview.1.1233.html#writing parse a manifest http://people.w3.org/mike/diffs/html5/spec/Overview.1.1233.html#parse1 5.7.3 The cache manifest syntax http://people.w3.org/mike/diffs/html5/spec/Overview.1.1233.html#manifests select an application cache http://people.w3.org/mike/diffs/html5/spec/Overview.1.1233.html#select0 http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1232&r2=1.1233&f=h http://html5.org/tools/web-apps-tracker?from=2047&to=2048 =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.1232 retrieving revision 1.1233 diff -u -d -r1.1232 -r1.1233 --- Overview.html 11 Aug 2008 22:55:11 -0000 1.1232 +++ Overview.html 11 Aug 2008 23:26:11 -0000 1.1233 @@ -1332,10 +1332,13 @@ <li><a href="#manifests"><span class=secno>5.7.3 </span>The cache manifest syntax</a> <ul class=toc> - <li><a href="#writing"><span class=secno>5.7.3.1. </span>Writing + <li><a href="#a-sample"><span class=secno>5.7.3.1. </span>A sample + manifest</a> + + <li><a href="#writing"><span class=secno>5.7.3.2. </span>Writing cache manifests</a> - <li><a href="#parsing1"><span class=secno>5.7.3.2. </span>Parsing + <li><a href="#parsing1"><span class=secno>5.7.3.3. </span>Parsing cache manifests</a> </ul> @@ -34073,7 +34076,42 @@ <h4 id=manifests><span class=secno>5.7.3 </span>The cache manifest syntax</h4> - <h5 id=writing><span class=secno>5.7.3.1. </span>Writing cache manifests</h5> + <h5 id=a-sample><span class=secno>5.7.3.1. </span>A sample manifest</h5> + + <p><em>This section is non-normative.</em> + + <p>This example manifest requires two images and a style sheet to be cached + and whitelists a CGI script. + + <pre>CACHE MANIFEST +# the above line is required + +# this is a comment +# there can be as many of these anywhere in the file +# they are all ignored + # comments can have spaces before them + # but most be alone on the line + +# blank lines are ignored too + +# these are files that need to be cached they can either be listed +# first, or a "CACHE:" header could be put before them, as is done +# lower down. +images/sound-icon.png +images/background.png +# note that each file has to be put on its own line + +# here is a file for the online whitelist -- it isn't cached, and +# references to this file will bypass the cache, always hitting the +# network (or trying to, if the user is offline). +NETWORK: +comm.cgi + +# here is another set of files to cache, this time just the CSS file. +CACHE: +style/default.css</pre> + + <h5 id=writing><span class=secno>5.7.3.2. </span>Writing cache manifests</h5> <p>Manifests must be served using the <code title="">text/cache-manifest</code> MIME type. All resources served using @@ -34201,7 +34239,7 @@ <p>URLs in manifests must not have fragment identifiers (i.e. the U+0023 NUMBER SIGN character isn't allowed in URLs in manifests). - <h5 id=parsing1><span class=secno>5.7.3.2. </span>Parsing cache manifests</h5> + <h5 id=parsing1><span class=secno>5.7.3.3. </span>Parsing cache manifests</h5> <p>When a user agent is to <dfn id=parse1>parse a manifest</dfn>, it means that the user agent must run the following steps:
Received on Monday, 11 August 2008 23:29:59 UTC