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

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

From: Robin Berjon <robin@robineko.com>
Date: Tue, 7 Sep 2010 15:05:17 +0100
Cc: public-device-apis@w3.org
Message-Id: <9B2983F7-D3C0-4EE3-B9AF-BDCE6B53271B@robineko.com>
To: Philip Gladstone <pgladstone@cisco.com>
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:


Robin Berjon
  robineko  hired gun, higher standards
Received on Tuesday, 7 September 2010 14:06:02 UTC

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