RE: W3C Working Draft for Data Store API

Hi Gene,

Great piece of work. Thanks. I have a few questions:
-How to ensure uniqueness of the DataStore 'name'?
-Any difference between 'add' providing an 'id' as argument and 'update' that is update (data, id) vs. add (data, id) ? In case no difference, do we need both?
-Have you thought about adding the additional parameter 'data' to DataStoreChangeEvent, so that the app can update on the fly when receiving the events. In case there is any reason not to do that, what is the value added by having 'id' and 'operation' in DataStoreChangeEvent, if the user needs to invoke DataStore.sync() anyway to perform the synchronization?

More comments may come once the work to adapt the Contacts and Messaging API starts. I assume that the working assumption is to make these adaptations, but please shout otherwise.

Regards,
Eduardo.


On 22 ene 2014 at 11:48:48, Gene Lian wrote:
> Hi SysApps,
>
> I've been working out a W3C working draft for the Data Store API,
> which is aimed to solve the issue that the Messaging API and
> the Contacts API might be facing: it's hard to define a general
> DB schema for searching/filtering messages/contacts.
>
>   http://airpingu.github.io/data-store-api/index.html

> I also made a github for it in my personal space (maybe it's better
> to move it to somewhere more formal):
>
>   https://github.com/airpingu/data-store-api

> Hope this can get noticed and please feel free to fire issues or
> questions about this draft.
>
> Thank you!
>
> Cheers,
> Gene

________________________________

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 Wednesday, 5 February 2014 10:53:41 UTC