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

RE: Contacts API and storage awareness (Re: ACTION-54)

From: SULLIVAN, BRYAN L (ATTCINW) <BS3131@att.com>
Date: Wed, 3 Mar 2010 06:19:11 -0800
Message-ID: <8080D5B5C113E940BA8A461A91BFFFCD10EE7101@BD01MSXMB015.US.Cingular.Net>
To: "Dominique Hazael-Massieux" <dom@w3.org>
Cc: "W3C Device APIs and Policy WG" <public-device-apis@w3.org>
Putting this at the OS/browser level means that the webapp can't be sure of the actual handling in any specific device. Thus when Bob or Alice switch devices, they have to go through a process of configuration checking, and it's possible that the other device won't support such an underlying control. Having this info visible and controllable by the webapp means that no matter what device they use, the same user experience is achievable since this is only dependent upon the webapp user preferences.

Thanks, 
Bryan Sullivan | AT&T

-----Original Message-----
From: Dominique Hazael-Massieux [mailto:dom@w3.org] 
Sent: Wednesday, March 03, 2010 12:15 AM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: W3C Device APIs and Policy WG
Subject: Contacts API and storage awareness (Re: ACTION-54)

Hi Bryan,

Le mardi 02 mars 2010 à 21:45 -0800, SULLIVAN, BRYAN L (ATTCINW) a
écrit :
> Provide use cases where contacts API needs to be aware of source of
> contacts:
> 
> Two basic use cases are:
> 
> 1) Bob wants to keep contacts on his SIM only. Thus the webapp that uses or updates Bob's contacts
> needs to know where the contacts are coming from, and where they will be
> written to.
> 
> 2) Alice wants to keep contacts on her device only. Thus the webapp that updates Alice's contacts needs to know
> where the contacts will be written to.

It's still not clear to me why this is something the WebApp itself needs
to know; I can imagine this kind of preferences being set in the browser
or at the OS level; I still don't know why each individual app would
need to deal with that aspect.

Dom

Received on Wednesday, 3 March 2010 14:19:48 GMT

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