W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2010

[Bug 10007] New: Async callbacks should fire in the same order the async requests are made in IndexedDB.

From: <bugzilla@jessica.w3.org>
Date: Thu, 24 Jun 2010 11:43:19 +0000
To: public-webapps@w3.org
Message-ID: <bug-10007-2927@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10007

           Summary: Async callbacks should fire in the same order the
                    async requests are made in IndexedDB.
           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, jonas@sicking.cc


Per the "[IndexedDB] Callback order" thread [1], we should specify the order of
async callbacks (either onsuccess or onerror) to fire in the order that the
async requests are made.  I.e. the same order the IDBRequest objects are
returned.

[1] http://www.mail-archive.com/public-webapps@w3.org/msg09208.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 Thursday, 24 June 2010 11:43:21 GMT

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