- From: Peter Kasting <pkasting@google.com>
- Date: Wed, 24 Feb 2010 11:23:12 -0800
On Wed, Feb 24, 2010 at 11:11 AM, Nicholas Zakas <nzakas at yahoo-inc.com>wrote: > I'm also less-than-thrilled with this being asynchronous, as I think the > use cases for cookies are vastly differently than those for databases and > web storage. The world is already parsing cookies synchronously right now, > it doesn't seem like asynchronicity buys much benefit, it just introduces an > additional level of indirection. You haven't just spent several tortuous weeks trying to figure out how on earth to correctly prompt for cookies in a multiprocess browser in a way that doesn't break synchronicity requirements the way we have. Synchronous access to state didn't cause many issues when browsers were all single-process, single-thread. That is increasingly not going to be the world we live in. As Jonas mentioned, just look at localStorage (which, contra your position, many developers have proposed using very much like cookies) for recent history of why synchronous APIs are troublesome. PK -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100224/5c9402e3/attachment.htm>
Received on Wednesday, 24 February 2010 11:23:12 UTC