W3C home > Mailing lists > Public > public-device-apis@w3.org > September 2010

Re: PendingOperation (was Re: CfC: The Media Capture API FPWD)

From: <Frederick.Hirsch@nokia.com>
Date: Tue, 21 Sep 2010 20:58:41 +0200
To: <rich.tibbett@gmail.com>
CC: <Frederick.Hirsch@nokia.com>, <robin@robineko.com>, <public-device-apis@w3.org>
Message-ID: <D92E5419-1C9A-4806-899E-57CE659BC08D@nokia.com>
if this affects multiple specs should PendingOperation  terminology and error handling approach be summarized in the API requirements document?

That does not necessarily mean taking anything out of Contacts

regards, Frederick

Frederick Hirsch

On Sep 21, 2010, at 7:03 AM, ext Rich Tibbett wrote:

On Tue, Sep 7, 2010 at 4:05 PM, Robin Berjon <robin@robineko.com<mailto:robin@robineko.com>> wrote:
On Sep 3, 2010, at 15:45 , Philip Gladstone wrote:
> * Is the cancel on the PendingOperation synchronous? I.e. once that
> method returns, has the PendingOperation been cancelled, or is it only
> canceled when (for example) the errorCB is called with a 'CANCELED'
> error status. If an image capture is cancelled once the user has
> captured one image, is that image lost, or does it get returned on a
> successCB? If it is lost, does it remain in persistent storage?

We need to better define PendingOperation across all our specs that use it. The first thing to note is that actually cancelling the device operation can only be a SHOULD  in some cases it can't be done without the UA being able to do much about it. What's important is that we make sure that the code behaviour is consistent and works for authors.

The second part is that we should define callback operations in terms of event loops, tasks, and task queues so as to ensure their interoperability (and integration). For more detail, see:


I took a stab at adding this second part in to the latest Contacts API ED. The CVS diff log is here: http://dev.w3.org/cvsweb/2009/dap/contacts/Overview.html.diff?r1=1.87&r2=1.88&f=h

I'm unclear whether we can (or you intended to) make PendingOperation the single event source for both success and error callbacks or whether we need separate event sources for each (the callback interfaces themselves). I opted for the former which will require changes to the Core Device Specification to reflect PendingOperations status as an event source.

Anyway, it's just a stab and if I got this right the first time around I'd be quite surprised.

Received on Tuesday, 21 September 2010 18:59:26 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:46 UTC