the difficulty with a named-section option is that the manifest generation for an application would have to know which users use a particular machine, which is pretty much a non-starter.<div><br></div><div>a<br><br><div class="gmail_quote">
On Tue, Jul 28, 2009 at 6:08 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">If the application code (HTML, JS, CSS) is all the same for two users,</div>
then appcache works for multiple users by just having the data for the<br>
users separate from the logic.<br>
<br>
This is the expected model for most apps. For example, your typical blog<br>
has just one set of CSS for all users.<br>
<br>
For systems where the user affects what HTML, JS, and CSS is served back,<br>
the spec as written pretty much requires that there be one app per user,<br>
and one generic "login" app that then redirects to one of those other apps<br>
-- and where each app has a different base URL, separate manifest, etc.<br>
<br>
I think conceptually that's actually not a bad idea anyway, to be honest.<br>
However, I could see that it might not be the preferred model.<br>
<br>
An alternative that we could explore in a future version is to have the<br>
manifest include a manifest name, and then have script that allows you to<br>
"activate" a particular manifest name for a given appcache.<br>
<br>
So each appcache group would be futher subdivided into named subgroups,<br>
and for a given manifest URL with such a group of subgroups, one subgroup<br>
would be the default one at a time. The inactive ones would just lie<br>
dormant, but and the active ones would act like now, but there'd be a<br>
scripted way to change the default (and maybe query what available<br>
variants exist for the current appcache), so that you could log back in as<br>
someone else by just making the script pick the other user's variant, and<br>
then reloading.<br>
<br>
I've noted this in the spec as a possible v2 feature.<br><font class="Apple-style-span" color="#888888"><br></font></blockquote></div>
</div>