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

[WebDatabase] Database interface (vs. DatabaseSync interface)

From: Nikunj R. Mehta <nikunj.mehta@oracle.com>
Date: Fri, 24 Jul 2009 18:51:19 -0700
Message-Id: <C40C2DC5-F254-429F-999C-AB026E714245@oracle.com>
To: public-webapps WG <public-webapps@w3.org>
It appears that Database, SQLTransactionCallback,  
SQLTransactionErrorCallback, SQLVoidCallback, SQLTransaction,  
SQLStatementCallback, and SQLStatementErrorCallback interfaces can all  
be eliminated from WebDatabase completely.

Given WebWorkers and DatabaseSync, why do we need the Database object  
at all? Are there use cases that cannot be satisfied by the  
combination of the two that?

There is a brand new programming model being promoted by the Database  
object, it is as complex as it gets and seriously I cannot get it. I  
don't know about you, but I doubt it will work for an average Web page  
author. Given its programming model, Oracle is not supportive of the  
asynchronous Database and related interfaces.

Received on Saturday, 25 July 2009 01:53:41 UTC

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