<div dir="ltr">Hi,<div><br></div><div>last week at our Face2Face we had a discussion about sync, moving forward on the client (will be a different thread) and on the server.</div><div><br></div><div>For the server-side we had a few different approaches:</div>
<div>1) AeroGear Sync-Server: Dan and Luke worked on the sync-server ([1]) as a 'long term' solution</div><div><div>The project contains two server implementations:</div><div>- RestServer implementation that uses a simple approach of rejecting conflicts and delegating the responsibility to resolve conflicts to the client.</div>
<div>- DiffServer Based on Google's Differential Synchonrization by Neil Fraser. This server is WebSocket based.</div><div><br></div><div><br></div><div>2) Initial quick and simple solution based on JAX-RS and JPA:</div>
</div><div><div>- We have versioning in JPA (optimistic locking) - Use it (send 409 on server and send right data)</div><div>-- Use JAX-RS ExceptionMapper for exceptions around the optimistic locking ?</div><div>- Client library will have helper methods for managing data</div>
<div>- Use push to send notifications that data changed?</div><div>- JAX-RS Annotation to send notifications?</div></div><div><br></div><div><br></div><div>I'd like to follow up on that, to see where things stand <br>
</div><div><br></div><div>Greetings,</div><div>Matthias</div><div><br></div><div><br clear="all"><div>[1] <a href="https://github.com/danbev/aerogear-sync-server/tree/differential-synchronization">https://github.com/danbev/aerogear-sync-server/tree/differential-synchronization</a></div>
-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>