W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

[Bug 10165] New: IDBRequest.abort() should throw on non-read-only requests or simply be removed

From: <bugzilla@jessica.w3.org>
Date: Wed, 14 Jul 2010 10:37:10 +0000
To: public-webapps@w3.org
Message-ID: <bug-10165-2927@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10165

           Summary: IDBRequest.abort() should throw on non-read-only
                    requests or simply be removed
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Indexed Database API
        AssignedTo: nikunj.mehta@oracle.com
        ReportedBy: jorlow@chromium.org
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org


As discussed in the thread "[IndexedDB] IDBRequest.abort on writing requests"
[1], it's dangerous to allow IDBRequest.abort() to be called on any request
that has side effects.  The best solution brought up in the thread was to have
it throw if you call it on any request that isn't read only.

But later on in the thread, I think it became fairly questionable that
IDBRequest.abort() provides any value in the current spec since none of the
read only operations should be particularly long running and in the few cases
where you might truly need to do an abort, you can simply roll back the
transaction.

[1] http://lists.w3.org/Archives/Public/public-webapps/2010JulSep/0190.html

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 14 July 2010 10:37:12 GMT

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