- From: EDUARDO FULLEA CARRERA <efc@tid.es>
- Date: Thu, 19 Sep 2013 16:10:36 +0000
- To: "Kis, Zoltan" <zoltan.kis@intel.com>, "public-sysapps@w3.org" <public-sysapps@w3.org>, Mounir Lamouri <mounir@lamouri.fr>, Jonas Sicking <jonas@sicking.cc>, Marcos Caceres <w3c@marcosc.com>, JOSE MANUEL CANTERA FONSECA <jmcf@tid.es>, "ch.dumez@sta.samsung.com" <ch.dumez@sta.samsung.com>
Hi Zoltan, On 28 ago 2013 at 20:25:57, Kis, Zoltan wrote: > Hello, > > Here is an attempt to use the DataStore concept in Messaging: > https://etherpad.mozilla.org/un9XkdXeKh > Thanks for the analysis. It looks ok to me, with one exception, we shouldn't get rid of the fetch method in MmsManager. This method is not related with the local storage but a request to fetch the message from the MMS Server. > For Call History, there are no changes needed. The Telephony spec > describes the structure of the call history, and the DataStore > interface provides access to it. > > Also, although I am not editor for Contacts API, I played with the idea > of using DataStore there, too: https://etherpad.mozilla.org/R2Xrl2253o > It looks fine to me. > Thinking through the use cases with Messaging and Contacts, I propose > small modifications to DataStore: > (see https://etherpad.mozilla.org/whatever-you-want, changes marked) > - use a new 'type' property, describing the type of the storage, e.g. > "contacts", "messaging", "call-history", "email", "im", etc (i.e. take > over the semantics of the former 'name' property) > - use the 'name' property with a changed semantics, denoting a > particular instance of the type of DataStore in question, e.g. > "addressbook1", "sim1-contacts", "facebook-contacts", "sms1", "mms", > "email-gmail-myusername", "email-yahoo-anotherusername", etc. Note > that this is orthogonal to partitioning the data over services (it is > possible, but not necessary). > > I think with these changes DataStore could be safely used for Messaging > and Contacts, satisfying the use cases both in FxOS and Tizen. > > Please advise whether is this a path we should apply to Messaging [, > Telephony, and Contacts]. > On paper it seems that it can work ok. It may be good though to wait until we hear some feedback from actual implementations, before rubberstamping it in the specs. > Best regards, > Zoltan ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx
Received on Thursday, 19 September 2013 16:12:06 UTC