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


From: Laxmi Narsimha Rao Oruganti <Laxmi.Oruganti@microsoft.com>
Date: Thu, 16 Jul 2009 21:45:15 +0800
To: "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <C84F9222BE3A34439A7F58655086DFD70CD196C11A@AA-EXMSG-C426.southpacific.corp.microsoft.com>
Hey folks,

                I have few questions on Web Storage Spec.  I have checked the content of both latest published spec<http://www.w3.org/TR/webstorage/> and  latest editors spec<http://dev.w3.org/html5/webstorage/>.  And the questions are applicable to both the versions of the spec.

                Section: 4.4.2 Processing model

1.       Open a new SQL transaction to the database, and create a SQLTransaction<http://www.w3.org/TR/webstorage/#sqltransaction> object that represents that transaction. If the mode is read/write, the transaction must have an exclusive write lock over the entire database. If the mode is read-only, the transaction must have a shared read lock over the entire database. The user agent should wait for an appropriate lock to be available.


-          Why is the spec mandating a transaction to take an *exclusive write lock on the entire database*?  No database book design mandates it.  In fact, many client databases out there don't do this.  I guess SQLite does this kind.  But that does not mean that all implementations have this nature.  I am kind of worried that we are putting implementation in theory.  For me they are too separate, there are many ways a database could be designed.  Like, log+checkpoint approach,  shadow copy, version store, journals ...etc.  I guess spec should say what a browser should do and not how.

I would be happy to get enlightened.

Received on Thursday, 16 July 2009 13:46:01 UTC

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