W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: IndexedDB, what were the issues? How do we stop it from happening again?

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Fri, 15 Mar 2013 04:10:15 +0100
To: Alex Russell <slightlyoff@google.com>
Cc: public-webapps@w3.org
Message-ID: <ph35k854i0e22m9u01hbkf54ff0rnbujln@hive.bjoern.hoehrmann.de>
* Alex Russell wrote:
>My *first* approach to this annoyance would be to start adding some async
>primitives to the platform that don't suck so hard; e.g., Futures/Promises.
>Saying that you should do something does not imply that doubling up on API
>surface area for a corner-case is the right solution.

http://lists.w3.org/Archives/Public/www-archive/2008Jul/0009.html was my
"first approach". Workers of course have it much easier, they just need
a single waiting primitive to make an asynchronous API synchronous. I've
http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/1016.html
argued against duplicating APIs for workers as proposed here, but so far
without much success, it would seem...
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Friday, 15 March 2013 03:10:43 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:58 GMT