Not sure what you are suggesting, Anne - it sounds like they want to tie the AppCache to a specific cookie/value combination, which I don't believe is supported by the current spec.<br><br>-atw<br><br><div class="gmail_quote">
On Wed, Jul 22, 2009 at 3:32 AM, Anne van Kesteren <span dir="ltr"><<a href="mailto:annevk@opera.com">annevk@opera.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Wed, 15 Jul 2009 00:30:05 +0200, Aaron Whyte <<a href="mailto:awhyte@google.com">awhyte@google.com</a>> wrote:<br>
> Most apps provide different contents for the same uncacheable main-page<br>
> URL, depending on the identity of the user, which is typically stored in a<br>
> cookie and read by the server.<br>
> However, the HTML5 AppCache spec doesn't allow cookies to influence the<br>
> choice of AppCaches or the contents of a response returned by the cache.<br>
<br>
</div>Why not? I cannot find anything like that in the specification. It seems to me that the generic fetching algorithm is used which does not forbid sending cookies and even explicitly calls out setting them.<br>
<font color="#888888"><br>
<br>
--<br>
Anne van Kesteren<br>
<a href="http://annevankesteren.nl/" target="_blank">http://annevankesteren.nl/</a><br>
</font></blockquote></div><br>