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

Re: [Bug 11348] New: [IndexedDB] Overhaul of the event model

From: Axel Rauschmayer <axel@rauschma.de>
Date: Fri, 28 Jan 2011 16:02:51 +0100
Message-Id: <DD06C9FA-3289-48DF-953C-F80EAD3B8D66@rauschma.de>
Cc: public-webapps WG <public-webapps@w3.org>
To: Shawn Wilsher <sdwilsh@mozilla.com>
>> Agreed. My only aside would be that for API design, itís usually not a good idea to listen to web developers, but to someone who has experience with designing DB APIs (= not me, but possibly anyone of you or anyone at Mozilla, MS, Google).
> It sounds like you are saying we aren't listening to people who have designed database APIs.  We certainly have (and have borrowed from models of existing APIs for other databases too).

I hope I was and am sounding constructive, I really appreciate the hard work that went into IndexedDB and am trying to understand the design rationales.

So far I have used APIs for JDBC, WebDatabase, RDF, and CouchDB. And they all seemed similar in the patterns they used (how functionality was invoked etc.). I was wondering why IndexedDB was so different. Until now, I have only seen events in bus-like constructs (Node.js event emitters, DOM events for DOM elements, custom DOM events for a complete web page, etc.).

-- 
Dr. Axel Rauschmayer
axel@rauschma.de
Home: http://rauschma.de
Blog: http://2ality.com
Received on Friday, 28 January 2011 15:03:20 GMT

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