- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Tue, 11 Jun 2013 14:25:35 -0400
- To: Kyaw Tun <kyawtun@yathit.com>
- CC: Webapps WG <public-webapps@w3.org>
Hi - your comment is considered a "Last Call comment" and it was included in the LC's comment tracking document [1]. In [2], Joshua proposed this comment be addressed/resolved as a feature request and as such, it was added to the IDB feature request list [3]. For the purposes of tracking your comment, please indicate if this resolution is acceptable or not. -Thanks, ArtB [1] <https://dvcs.w3.org/hg/IndexedDB/raw-file/default/Comments-16-May-2013-LCWD.html> [2] <http://lists.w3.org/Archives/Public/public-webapps/2013AprJun/0817.html> [3] <http://www.w3.org/2008/webapps/wiki/IndexedDatabaseFeatures> On 5/19/13 9:37 PM, ext Kyaw Tun wrote: > Sorry for reposting again for > http://lists.w3.org/Archives/Public/public-webapps/2013AprJun/0422.html Perhaps > I am not well explain enough. > > In put and add method of object store and index, DataCloneError and > DataError are immediately throw before executing IDBRequest. It seems good > that exception are throw immediately, but in practical use case, these > exception are in async workflow (inside transaction callback). Exception > break the async workflow, (of course, it depending on usage design > pattern). > > DataCloneError and DataError are preventable in most situation. But > sometimes tricky. We even want database to handle these errors like > database constraint. The logic will be much simpler if DataCloneError > and DataError cause to invoke IDBRequest.onerror rather than exception.
Received on Tuesday, 11 June 2013 18:26:04 UTC