<div class="gmail_quote">On Tue, Apr 7, 2009 at 6:33 PM, Brady Eidson <span dir="ltr"><<a href="mailto:beidson@apple.com">beidson@apple.com</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"><br>
On Apr 7, 2009, at 6:24 PM, Jeremy Orlow wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Both would lead to bizarre behavior where data that the application thought was saved really wasn't.<br>
<br>
This matches up with how most private browsing sessions handle cookies, right? The data persists until the session is up (because some of the web can't work correctly without them) but then they're deleted at the end.<br>
</blockquote>
<br></div>
I guess I'll raise this point yet again, as it's a favorite of mine... ;) Cookies are not expected to be persistent, and when space runs out for them and they're expired there is already no notification of that. Any app writer that expected cookies to be a safe, persistent store of data or state was already playing with fire.</blockquote>
<div><br></div><div>(Sorry. I started that email, walked away a bit, and sent it before seeing the torrent of responses.) </div><div><br></div><div>I still think it's a valid point that, whether or not the intention for cookies, many web apps assume that they are not so volatile. And, in practice, this is generally a safe assumption.</div>
</div>