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

[IndexedDB] onsuccess isn’t the best for writes

From: Yonathan <yonathan@gmail.com>
Date: Fri, 16 Mar 2012 04:24:19 -0700
Message-ID: <CAAavymc11NVhv_pGbATOqvWW9SG944aJiZ81RPtT4AnYHvv8Gw@mail.gmail.com>
To: public-webapps@w3.org
I’m concerned that people will listen to IDBRequest’s “success” event
to notify when an add or put has been successfully written. For
example, the “Using IndexedDB” article[1] recommends, “The first thing
you'll want to do with almost all of the requests you generate is to
add success and error handlers:” Instead, as far as I can tell,
success listeners should only be added to read requests (get, count,
and openCursor after each continue and advance), whereas for write
requests you should almost always listen to the transaction’s
“complete” event instead. The reason is that after a request succeeds,
the transaction as a whole may yet fail due to UnknownError, as well
as abort or an error in a later request on the same transaction if you
don’t preventDefault(). Should the specification encourage onsuccess
for reads and oncomplete for writes?

  [1]: https://developer.mozilla.org/en/IndexedDB/Using_IndexedDB

Yonathan Randolph
Received on Monday, 19 March 2012 07:36:05 GMT

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