W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2011

Re: The reason PendingOp removed from Messaging API

From: Robin Berjon <robin@berjon.com>
Date: Mon, 14 Nov 2011 12:08:54 +0100
Cc: "kisubs.song@samsung.com" <kisubs.song@samsung.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-Id: <0C22614B-AFBB-4F2B-9CDA-B2A33CFCC255@berjon.com>
To: Travis Leithead <Travis.Leithead@microsoft.com>
Hi all,

On Nov 11, 2011, at 22:44 , Travis Leithead wrote:
>> -----Original Message-----
>> From: Kisub Song [mailto:kisubs.song@samsung.com]
>> Sent: Thursday, November 10, 2011 10:05 PM
>> I found that the PendingOp had existed on the previous version of Messaging
>> API.
>> But it was removed from latest version.
>> 
>> Is there any reasons for this decision?
> 
> I was also curious, but when I checked the earlier spec, I noticed that it was used without being defined. Was it ever defined? If not, that's my guess at why it was removed :)

PendingOp was (very quickly) defined in "Core Device Interfaces":

    http://dev.w3.org/2009/dap/device/

That draft was never officially published. We removed PendingOp because we had feedback that in most cases in which it was used there were potential issues with cancelling operations (i.e. it might not be possible, and it might provide a false sense of security that something actually has been cancelled).

Is there any specific reason why this is resurfacing? We can always look at reinstating it if needed (though I'd rather avoid flip-flopping too much :).

Note that WebApps has on occasion discussed using Promises for async calls (e.g. http://lists.w3.org/Archives/Public/public-webapps/2010JanMar/0661.html), a topic which was also briefly mentioned during their TPAC f2f. Promises do more than PendingOp, but they're a natural tie-in (I think). Based on feedback to date it seems to be one of those ideas that has neither strong support nor strong opposition, so that nothing happens with regards to it. If there's interest in using Promises, the idea needs a champion. That would involve:

    1) talking to the people currently working on APIs that could use them (not necessarily all of them, but at least a decent cross-section) to see how amenable they are to the idea;
    2) probably writing some examples for those specs to show that it works, is elegant, etc.;
    3) ask developers for feedback about this (the ScriptLib CG would be the right place for this);
    4) draft a Promises API (which shouldn't be too much work  famous last words, I know).

-- 
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Monday, 14 November 2011 11:09:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:24 GMT