Re: DataStore, applied in Messaging, Telephony (and Contacts) API

Hi Eduardo,

Thank you for reviewing these.

>  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.

Indeed. My mistake.

>> 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.

Yes, the DataStore itself needs some more separate discussion, and
also we need to go through how to solve the use cases with it.
It was good to hear that it solved the problem for Mozilla. We also
need to analyse if it is good for Tizen (and what changes it brings in
addition, or instead of the proposed ones). Feedback from others would
be welcome, too.

Best regards,
Zoltan

Received on Thursday, 19 September 2013 17:50:49 UTC