W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2010

[Bug 11425] New: [IndexedDB] Transaction timeout parameter should probably be a double

From: <bugzilla@jessica.w3.org>
Date: Mon, 29 Nov 2010 11:47:55 +0000
To: public-webapps@w3.org
Message-ID: <bug-11425-2927@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11425

           Summary: [IndexedDB] Transaction timeout parameter should
                    probably be a double
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Indexed Database API
        AssignedTo: dave.null@w3.org
        ReportedBy: jorlow@chromium.org
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org


Right now, the transaction timeout parameter is an unsigned long with no time
equivalent to infinity and no way (other than omission) to use the browsers
default.  Unsigned long is also kind of an odd type to use in a JavaScript API.

Maybe this should be a double instead.  Positive infinity could mean "no
timeout".  0 and/or negative could mean browser default and/or throw an
exception.  (I don't care much either way.)

Note that Geolocation uses a double for their timeout parameter.  In that case,
0 means to timeout immediately if there's no cached value.  In IndexedDB, it
seems as though the analog would be like a try lock (i.e. run the transaction
if we can without waiting at all), but I'm not sure that has much benefit and
it would be adding non-deterministic surface area which seems bad.

-- 
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 Monday, 29 November 2010 11:47:57 GMT

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