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

Serializing Asynchronous API calls (was: API patterns and requirements)

From: Dominique Hazael-Massieux <dom@w3.org>
Date: Thu, 17 Jun 2010 16:42:32 +0200
To: Rich Tibbett <rich.tibbett@gmail.com>
Cc: public-device-apis@w3.org
Message-ID: <1276785752.2228.6.camel@localhost>
Le jeudi 17 juin 2010 à 15:23 +0100, Rich Tibbett a écrit :
> On the other hand, in order to ensure a reasonable user experience
> (i.e. don't bombard the user with more than one permission request at
> a time) I think we should include a requirement for serial access to
> each API (or collectively, all APIs) - that no more than one API call
> should be executable concurrently. I'd like to explore if this is a
> reasonable assumption for e.g. Contacts and whether any changes to the
> pattern used may be required for this.

That seems indeed likely a fairly important aspect to look at, thanks
for bringing it up.

It makes it slightly more awkward to use as a developer, but I don't
think to the point of making it painful. And it does seem to solve a
possibly thorny issue.

Note that it's not obvious that it should be applied both to Contacts
and SysInfo — I don't know if the intent is that SysInfo calls would
require user authorization for each, or just one before the first call,
or none at all.

I wonder how the current Mozilla implementation of the Contacts API deal
with that aspect — have you looked into it?

Dom
Received on Thursday, 17 June 2010 14:42:47 GMT

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