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

[Bug 10357] New: [IndexedDB] Remove the SNAPSHOT_READ transaction mode

From: <bugzilla@jessica.w3.org>
Date: Thu, 12 Aug 2010 23:51:26 +0000
To: public-webapps@w3.org
Message-ID: <bug-10357-2927@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10357

           Summary: [IndexedDB] Remove the SNAPSHOT_READ transaction mode
           Product: WebAppsWG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Indexed Database API
        AssignedTo: nikunj.mehta@oracle.com
        ReportedBy: pablo.castro@microsoft.com
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org


We currently have two read-only transaction modes, READ_ONLY and SNAPSHOT_READ,
that are identical in every aspect (point-in-time consistency for readers,
allow multiple concurrent readers, etc.), except that they have different
concurrency characteristics, with READ_ONLY blocking writers and SNAPSHOT_READ
allowing concurrent writers come and go while readers are active. 

We agreed (see [1]) that we could remove the concept and only have READ_ONLY,
leaving it up to the implementation whether writers block readers or readers
are allowed and some mechanism is used to maintain point-in-time consistency
semantics.

[1] http://lists.w3.org/Archives/Public/public-webapps/2010JulSep/0485.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, 12 August 2010 23:51:28 GMT

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