[aerogear-dev] Sync Data model

[Summers Pittman]

On 02/10/2014 10:06 AM, Corinne Krych wrote:
> On 10 Feb 2014, at 15:49, Summers Pittman <supittma at redhat.com> wrote:
>
>> On 02/10/2014 07:41 AM, Daniel Bevenius wrote:
>>> Hi,
>>>
>>> I've done some work on [1] in regards to coming up with a common sync data format for our clients, but I and messed it up [2]. Long story short is that I did not take into account some of client languages features. So here is a new suggestion that will hopefully work with all our client languages:
>>>
>>> public interface SyncObject<T, ID> {
>>>      ID objectId();
>>>      String revision();
>>>      T content();
>>> }
>>> What do people think about this?
>> One of the things I'm wondering about is, in the far far future
> in the far far future we’ll review the API. 2.0.
>
> I’ll rather to stick to what we need for M1/M2 to start with...
https://issues.jboss.org/browse/AEROGEAR-1409

^^ The future which is the second epic in the list.
>
>
>> when our code is told we have the server push^H^H^H^H asynchronously notifying the device of data changes, how will Java know what type the data coming in is?  It MAY be useful to have a name space feature in the message.
>
>
>>>
>>> [1] https://issues.jboss.org/browse/AEROGEAR-1406
>>> [2] https://github.com/aerogear/aerogear.org/commit/5e81e5526b5850485eeb83a8ff7ddc1e4d6d2c40
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>>
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev