<div dir="ltr">my understand was that the main focus is now on the real-time sync, leveraging out differential synchronization engine. <div><br></div><div>This reflects also the current move of removing the 'rest sync' module</div><div><a href="https://github.com/aerogear/aerogear-sync-server/commit/5fe0b240d646ef57c5927f726c6bf2c04aa5d3cc">https://github.com/aerogear/aerogear-sync-server/commit/5fe0b240d646ef57c5927f726c6bf2c04aa5d3cc</a> </div><div><br></div><div>-Matthias</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 15, 2014 at 5:31 PM, Lucas Holmquist <span dir="ltr"><<a href="mailto:lholmqui@redhat.com" target="_blank">lholmqui@redhat.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So i have some concerns on the Current state of the conflit resolution POC that i created.<br>
<br>
in it's current state, i had 3 methods in the api<br>
<br>
* Read - just a GET<br>
* Save - PUT/POST with an added "conflict" callback to handle the conflict resolution<br>
* Remove - just a DELETE<br>
<br>
This was all done before we wrote this spec<br>
<br>
<a href="https://aerogear.org/docs/planning/roadmaps/AeroGearConflictResolution/" target="_blank">https://aerogear.org/docs/planning/roadmaps/AeroGearConflictResolution/</a><br>
<br>
but even then, from the JS client perspective, it felt a lot like a pipe. In jQuery.ajax, you can actually listen for a "409".<br>
<br>
The other thing that concerns me is that on the client side, people are using frameworks such as Ember, Angular, Backbone,etc... that have there own ways of doing server requests so i would hate to start re-inveting the wheel again.<br>
<br>
while the read/remove don't really do anything different(they are just GET/DELETE's), the save method(PUT/POST) does. This is were all the "conflict resolution happens”. (what type on resolution algorithm, auto-merge, etc...)<br>
<br>
I think it would be interesting to try to integrate this part into existing frameworks, rather than trying to create Pipeline again.<br>
<br>
i think for node.js this might be interesting too, since we could create a piece of middleware that hooks into an express/connect request<br>
<br>
<br>
Again, this might only be a concern on the JS client side, not sure what the other platforms are like in this regard<br>
<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote></div><br clear="all"><div><br></div>-- <br><div class="gmail_signature">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>