This proposal is just java based client API, if we nail down how a user could build an app that has sync functionality, all other things will fall into place. I suggest we keep the protocol and the server implementation as simple as possible and like qmx also suggested. JSON based with a hash as revision number for merging.
On 9 Dec,2013, at 14:30 , Sebastien Blanc <scm.blanc@gmail.com> wrote:
_______________________________________________
On Mon, Dec 9, 2013 at 2:27 PM, Summers Pittman <supittma@redhat.com> wrote:
On Mon 09 Dec 2013 02:44:59 AM EST, Erik Jan de Wit wrote:So this would also require a server definition?
> My idea was that when the client calls sync the server side state and the client side state get merged and the delta is send
I have the same interrogations, what do we want do deliver :
- an Unified Synch Server ( USS )
- Client Libs (ios, android, web, cordova plugin)
>
> On 6 Dec,2013, at 18:16 , Summers Pittman <supittma@redhat.com> wrote:
>
>> One of the questions I have about this API is how are push events handled with sync or is this just an offline cache?
>>
>> IE how is data sent down to the client when things change (or is that not for this use case)
>>
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________ aerogear-dev mailing list aerogear-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev