[aerogear-dev] [datasync] Diffsync demo screencast

[Lukáš Fryč]

On Tue, Nov 11, 2014 at 4:19 PM, Daniel Bevenius <daniel.bevenius at gmail.com>
wrote:

> >Does this address the offline/online scenario?
> In one way it does but I think offline will demand more work. All clients
> have what is currently called a sync-engine which is responsible for
> performing the diffs/sync stuff and also storing of data. How data is
> stored is then decided by the sync-client which in addition implements the
> networking that will be used. So, the current clients are all WebSocket
> based but we could provide others that use a native networking transport
> where available.  At least that is the idea.
> Not sure if that makes sense and you are right a diagram would help. Let
> me see what I can do.
>
> >I assume the server-side database is also being updated?
> Yep, but at the moment we are only we only providing an in-memory
> datastore. But we can provide different storage options similar to what we
> do for Simple Push at the moment.
>

Btw  at this point we do not specifically address how the Realtime Sync
Server synchronizes data to the custom backend store.
I.e. a storage that Dan is talking about is a standalone storage that is
fully owned by the Sync Server (currently in-memory, but I'm working on poc
of Infinispan integration).

For synchronization with custom backends (be it REST endpoint, LiveOak,
...), we would need to allow concept of adapters / connectors (that are
capable of bidirectional updates/change notifications).

http://aerogear.org/docs/planning/roadmaps/AeroGearDataSync/


For the custom backend scenario, we rather plan to offer Conflict
Resolution concept:

http://aerogear.org/docs/planning/roadmaps/AeroGearConflictResolution/


>
>
>
> On 11 November 2014 16:05, Matthias Wessendorf <matzew at apache.org> wrote:
>
>> Dan,
>>
>> thanks a lot for sharing the early content we have. This is extremely
>> cool stuff! PLUS PLUS
>>
>> On Tue, Nov 11, 2014 at 12:04 PM, Daniel Bevenius <
>> daniel.bevenius at gmail.com> wrote:
>>
>>> Hi,
>>>
>>> just wanted to share a short screen cast of the demos we have for the
>>> diffsync POC:
>>>
>>> https://drive.google.com/file/d/0B2E1HZ1JnrJfNmFVcWZUWmM5Snc/view?usp=sharing
>>>
>>> This is just to show what is there at the moment as setting this up and
>>> running locally involves building the server locally, a bunch of iOS
>>> submodules, etc (pretty painful).
>>> This is still very much a work in progress but hopefully this will allow
>>> us to validate ideas and try things out as we move forward.
>>>
>>> The repos involved are:
>>>
>>> https://github.com/danbev/aerogear-sync-server/tree/differential-synchronization/diffsync
>>> https://github.com/danbev/aerogear-ios-sync-demo
>>> https://github.com/danbev/android-diffsync-demo
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141111/be95d3fb/attachment.html