And as of right now, afaict, a user / user agent can prune a database and not be in violation of the database spec :)<br><br><div class="gmail_quote">On Tue, Apr 7, 2009 at 6:11 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 style="word-wrap:break-word"><div class="im"><br><div><div>On Apr 7, 2009, at 6:09 PM, Ian Fette ($B%$%"%s%U%'%C%F%#(B) wrote:</div>
<blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<font color="#000000"><br></font> </blockquote> <br></div> I strongly share Jonas' concern that we'd tell web applications that we're storing there data when we already know we're going to dump it later. For 3 and 4 both, we're basically lying to the application and therefore the user. Imagine a scenario where a user has no network connection and unknowingly left their browser in private browsing mode. Email, documents, financial transactions, etc could all be "saved" locally then later thrown away before they've had a chance to sync to a server.<div>
</div></blockquote><div><br></div><div>The same argument could be made for retaining cookies set during private browsing ;-)</div></div></blockquote><br></div></div><div>I disagree, as cookies are already specified to be of unspecified persistence. I believe a user agent can - at any time - prune cookies from it's cookie store and not be in violation of the cookies spec.</div>
<div><br></div><font color="#888888"><div>~Brady</div></font></div></blockquote></div><br>