On Tue, 22 Dec 2009 03:43:21 +0100, Adrian Bateman
adria...@microsoft.com wrote:
Microsoft supports publishing a new Working Draft.
As does Opera (sorry, I have been offline)
cheers
Chaaks
On Monday, December 14, 2009 12:54 PM, Arthur Barstow wrote:
This is a Call for Consensus (CfC)
Hi Art, All,
I am sorry for my delayed response re VM-MF/-I.
I will be happy include the proposals from Vodafone into the original documents.
The interface parts will go into VMI, I think.
In [1] I promised deeper review of the VM principles (CSS, CSSOM) and this task
is still pending on me.
I
On December 22 WebApps published the following Last Call Working
Drafts (LCWD):
1. Server-Sent Events
http://www.w3.org/TR/2009/WD-eventsource-20091222/
2. Web Storage
http://www.w3.org/TR/2009/WD-webstorage-20091222/
3. Web Workers
http://www.w3.org/TR/2009/WD-workers-20091222
Hi Adrian,
I have published a non-JS version of the same document as the pub-
ready WD. You can take a look at it:
http://dev.w3.org/2006/webapi/WebSimpleDB/
I hope that works for you.
Nikunj
On Dec 21, 2009, at 6:58 PM, Adrian Bateman wrote:
On Monday, December 21, 2009 6:43 PM, I wrote:
On Tuesday, December 22, 2009 2:39 PM, Nikunj R. Mehta wrote:
Hi Adrian,
I have published a non-JS version of the same document as the pub-
ready WD. You can take a look at it:
http://dev.w3.org/2006/webapi/WebSimpleDB/
I hope that works for you.
Nikunj
Looks good. Thanks Nikunj.
My apologies for my late reply, I've been out for a while.
-Original Message-
From: Nikunj R. Mehta [mailto:nikunj.me...@oracle.com]
Sent: Friday, December 11, 2009 10:47 AM
To: public-webapps@w3.org WG
Cc: Pablo Castro
Subject: Re: [WebSimpleDB] Allowing schema operations anywhere
Whenever we take a callback that's to be called for each item in a set (e.g.
with a .forEach(callback) pattern), we need a way to indicate the system
whether it's ok to move to the next row and invoke the next callback or not.
Otherwise, in scenarios where the callback itself performs an
On Dec 22, 2009, at 5:39 PM, Pablo Castro wrote:
Whenever we take a callback that's to be called for each item in a
set (e.g. with a .forEach(callback) pattern), we need a way to
indicate the system whether it's ok to move to the next row and
invoke the next callback or not. Otherwise, in
