This type of request (see forwarded message below) to utilize the application cache for subresource loads into documents that are not stored in the cache has come up several times now. The current feature set is very focused on the "offline" use case. Is it worth making additions such that a document that loads from a server can utilize the resources in an appcache?<div>
<br></div><div>Today we have <html manifest="manifestFile">, which adds the document containing this tag to the appcache and associates that doc with that appcache such that subresource loads hit the appcache.</div>
<div><br></div><div>Not a complete proposal, but... </div><div><br></div><div>What if we had something along the lines of <html useManifest=''manifestFile">, which would do the association of the doc with the appcache (so subresources loads hit the cache) but not add the document to the cache?</div>
<div><br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">UVL</b> <span dir="ltr"><<a href="mailto:andrea.doimo@gmail.com">andrea.doimo@gmail.com</a>></span><br>
Date: Sun, Dec 19, 2010 at 1:35 PM<br>Subject: [chromium-html5] Application Cache for on-line sites<br>To: Chromium HTML5 <<a href="mailto:chromium-html5@chromium.org">chromium-html5@chromium.org</a>><br><br><br>I tried to use the HTML5 Application Cache to improve the performances<br>
of on-line sites (all the tutorials on the web write only about usage<br>
with off-line apps)<br>
<br>
I created the manifest listing all the js, css and images, and the<br>
performances were really exciting, until I found that even the page<br>
HTML was cached, despite it was not listed in the manifest. The pages<br>
of the site are in PHP, so I don't want them to be cached.<br>
<br>
>From <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html" target="_blank">http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html</a><br>
:<br>
"Authors are encouraged to include the main page in the manifest also,<br>
but in practice the page that referenced the manifest is automatically<br>
cached even if it isn't explicitly mentioned."<br>
<br>
Is there a way to have this automating caching disabled?<br>
<br>
Note: I know that caching can be controlled via HTTP headers, but I<br>
just wanted to try this way as it looks quite reliable, clean and<br>
powerful.<br>
<font color="#888888"><br>
--<br>
You received this message because you are subscribed to the Google Groups "Chromium HTML5" group.<br>
To post to this group, send email to <a href="mailto:chromium-html5@chromium.org">chromium-html5@chromium.org</a>.<br>
To unsubscribe from this group, send email to <a href="mailto:chromium-html5%2Bunsubscribe@chromium.org">chromium-html5+unsubscribe@chromium.org</a>.<br>
For more options, visit this group at <a href="http://groups.google.com/a/chromium.org/group/chromium-html5/?hl=en" target="_blank">http://groups.google.com/a/chromium.org/group/chromium-html5/?hl=en</a>.<br>
<br>
</font></div><br></div>