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

Device task source

From: Robin Berjon <robin@berjon.com>
Date: Wed, 30 Mar 2011 18:52:31 +0200
Message-Id: <B0C557ED-EB72-457D-8986-BACC2FB02821@berjon.com>
To: public-device-apis@w3.org
Hi,

the Contacts draft currently refers to a "device task source". It uses it notably in its find operation, where if there's an existing ongoing task from this source an error is dispatched.

The problem is that this is a generic task source (at least in name), which means that Calendar, for instance, would also use it. But it doesn't make sense to error on contacts.find() if I call calendar.findEvent().

So is the solution to:

  a) have different task sources for each spec (in which case a name change is in order);
  b) have the cancellation trigger only if a similar operation is ongoing.

I'm thinking (b). I can implement this change once we agree (I have to massage the whole task source situation anyway).

-- 
Robin Berjon - http://berjon.com/
Received on Wednesday, 30 March 2011 16:53:03 GMT

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