>> 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 [email protected] Home: http://rauschma.de Blog: http://2ality.com
