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

[Bug 12438] New: Sync API for setVersion should specify a callback method and timeout value

From: <bugzilla@jessica.w3.org>
Date: Wed, 06 Apr 2011 17:38:02 +0000
To: public-webapps@w3.org
Message-ID: <bug-12438-2927@http.www.w3.org/Bugs/Public/>

           Summary: Sync API for setVersion should specify a callback
                    method and timeout value
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Indexed Database API
        AssignedTo: dave.null@w3.org
        ReportedBy: israelh@microsoft.com
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org

IDBatabaseSync.setVersion assumes that the scope of the transaction it is
working on is the code that follows the API.  The current approach introduces
the possibility of deadlocks.  

In addition, there is no way to specify the timeout of the SET_VERSION

Modify the existing setVersion API to include an IDBTransactionCallback
parameter together with a timeout value parameter.

IDBTransactionSync setVersion ([TreatNullAs=EmptyString] in DOMString version,
in IDBTransactionCallback callback, in optional unsigned long timeout);

Parameter #2:
* callback
* Defines the method in which a VERSION_CHANGE transaction will be valid.

Parameter #3:
* timeout
* Defines a transaction timeout value in milliseconds that will limit the
lifetime of the VERSION_CHANGE transaction.  If the parameter is not provide,
the timeout value will be infinite.

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, 6 April 2011 17:38:06 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:31 UTC