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

Re: [WebDatabase] Database interface (vs. DatabaseSync interface)

From: Nikunj R. Mehta <nikunj.mehta@oracle.com>
Date: Mon, 27 Jul 2009 20:07:43 -0700
Cc: Maciej Stachowiak <mjs@apple.com>, Aaron Boodman <aa@google.com>, public-webapps WG <public-webapps@w3.org>
Message-Id: <C8436B0A-E6F1-4904-AE04-AC27A9E41124@oracle.com>
To: Jonas Sicking <jonas@sicking.cc>

On Jul 27, 2009, at 7:45 PM, Jonas Sicking wrote:

> On Mon, Jul 27, 2009 at 2:32 PM, Maciej Stachowiak<mjs@apple.com>  
> wrote:
>>
>> On Jul 27, 2009, at 2:14 PM, Nikunj R. Mehta wrote:
>>
>>>
>>> And mine did get awkward, very quickly. I found it really hard to  
>>> keep
>>> myself sane through the development of asynchronous code that  
>>> executes
>>> transactionally and involves multiple sql statements.
>>>
>>> My argument is that the program logic gets really complex, really  
>>> fast if
>>> you are doing anything complex using Database. On the other hand,  
>>> if your
>>> logic and SQL needs are really simple, you might as well use the
>>> DatabaseSync interface and pay the price of marshaling and  
>>> unmarshaling,
>>> which may not be that much.
>>
>> Aaron showed that it's pretty complex to implement the marshalling  
>> in a
>> general way on top of Workers and a synchronous interface.
>
> Also note that an API layered on top of Workers and a synchronous
> interface will still be an asynchronous API.


Understood. I am simply asking to not standardize "something which can  
be easily implemented in JavaScript", until we understand the  
implications of the novel programming model being proposed.

Nikunj
http://o-micron.blogspot.com
Received on Tuesday, 28 July 2009 03:10:19 GMT

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