'Named' cache groups under a single manifest url is an interesting idea. Presumably the webapp would be generating the 'name' in the manifest file based on a cookie value.<div><br></div><div>Another possibility is something along the lines of what is proposed in the DataCache draft: the manifest indicates a cookie name, and the value of that cookie determines the 'name' of the subgroup. And the value of that cookie also determines which subgroup is enabled at any given time.<br>
<br><div class="gmail_quote">On Tue, Jul 28, 2009 at 9:04 PM, Ian Hickson <span dir="ltr"><<a href="mailto:ian@hixie.ch">ian@hixie.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tue, 28 Jul 2009, Adam de Boor wrote:<br>
><br>
> the difficulty with a named-section option is that the manifest generation<br>
> for an application would have to know which users use a particular machine,<br>
> which is pretty much a non-starter.<br>
<br>
</div>I meant that each named appcache would have a separate manifest, and the<br>
manifest would just say the name of the one it was setting up.<br>
<div><div></div><div class="h5"><br>
--<br>
Ian Hickson U+1047E )\._.,--....,'``. fL<br>
<a href="http://ln.hixie.ch/" target="_blank">http://ln.hixie.ch/</a> U+263A /, _.. \ _\ ;`._ ,.<br>
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'<br>
</div></div></blockquote></div><br></div>