[aerogear-dev] how about this API for sync?

[Summers Pittman]

On 12/09/2013 09:56 AM, Erik Jan de Wit wrote:
> 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.

For real time sync this is a great primer: 
https://neil.fraser.name/writing/sync/.  The concepts can be expanded 
beyond text of course.

I guess my question is do we want a really low level but universal 
protocol which requires server support, or several separate APIs which 
can handle legacy servers, servers with minor changes, or real time 
capable servers?

As examples:
Legacy Servers can be periodic pollers.
Minor changes can be a sync on push type thing.
And realtime, is well, real time.

>
> On 9 Dec,2013, at 14:30 , Sebastien Blanc <scm.blanc at gmail.com 
> <mailto:scm.blanc at gmail.com>> wrote:
>
>>
>>
>>
>> On Mon, Dec 9, 2013 at 2:27 PM, Summers Pittman <supittma at redhat.com 
>> <mailto:supittma at redhat.com>> wrote:
>>
>>     On Mon 09 Dec 2013 02:44:59 AM EST, Erik Jan de Wit wrote:
>>     > 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
>>     So this would also require a server definition?
>>
>> 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 at redhat.com
>>     <mailto:supittma at 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 at lists.jboss.org <mailto:aerogear-dev at lists.jboss.org>
>>     https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org <mailto: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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20131209/1bef02d0/attachment.html