<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 16, 2014, at 6:41 AM, Matthias Wessendorf &lt;<a href="mailto:matzew@apache.org" class="">matzew@apache.org</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">my understand was that the main focus is now on the real-time sync, leveraging out differential synchronization engine.&nbsp;</div></div></blockquote><div><br class=""></div><div>i was not aware of that. &nbsp;I was under the understanding that both would be done in parallel since conflict resolution might be the solution for many people</div><div><br class=""></div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">This reflects also the current move of removing the 'rest sync' module</div><div class=""><a href="https://github.com/aerogear/aerogear-sync-server/commit/5fe0b240d646ef57c5927f726c6bf2c04aa5d3cc" class="">https://github.com/aerogear/aerogear-sync-server/commit/5fe0b240d646ef57c5927f726c6bf2c04aa5d3cc</a>&nbsp;</div><div class=""><br class=""></div><div class="">-Matthias</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, Dec 15, 2014 at 5:31 PM, Lucas Holmquist <span dir="ltr" class="">&lt;<a href="mailto:lholmqui@redhat.com" target="_blank" class="">lholmqui@redhat.com</a>&gt;</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 class="">
<br class="">
in it's current state, i had 3 methods in the api<br class="">
<br class="">
* Read - just a GET<br class="">
* Save - PUT/POST with an added "conflict" callback to handle the conflict resolution<br class="">
* Remove - just a DELETE<br class="">
<br class="">
This was all done before we wrote this spec<br class="">
<br class="">
<a href="https://aerogear.org/docs/planning/roadmaps/AeroGearConflictResolution/" target="_blank" class="">https://aerogear.org/docs/planning/roadmaps/AeroGearConflictResolution/</a><br class="">
<br class="">
but even then,&nbsp; from the JS client perspective, it felt a lot like a pipe.&nbsp; In jQuery.ajax,&nbsp; you can actually listen for a "409".<br class="">
<br class="">
The other thing that concerns me is that on the client side, people are using frameworks such as Ember, Angular, Backbone,etc...&nbsp; &nbsp;that have there own ways of doing server requests so i would hate to start re-inveting the wheel again.<br class="">
<br class="">
while the read/remove don't really do anything different(they are just GET/DELETE's), the save method(PUT/POST) does.&nbsp; This is were all the "conflict resolution happens”.&nbsp; (what type on resolution algorithm, auto-merge, etc...)<br class="">
<br class="">
I think it would be interesting to try to integrate this part into existing frameworks, rather than trying to create Pipeline again.<br class="">
<br class="">
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 class="">
<br class="">
<br class="">
Again, this might only be a concern on the JS client side,&nbsp; not sure what the other platforms are like in this regard<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
aerogear-dev mailing list<br class="">
<a href="mailto:aerogear-dev@lists.jboss.org" class="">aerogear-dev@lists.jboss.org</a><br class="">
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank" class="">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote></div><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature">Matthias Wessendorf <br class=""><br class="">blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank" class="">http://matthiaswessendorf.wordpress.com/</a><br class="">sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank" class="">http://www.slideshare.net/mwessendorf</a><br class="">twitter: <a href="http://twitter.com/mwessendorf" target="_blank" class="">http://twitter.com/mwessendorf</a></div>
</div>
_______________________________________________<br class="">aerogear-dev mailing list<br class=""><a href="mailto:aerogear-dev@lists.jboss.org" class="">aerogear-dev@lists.jboss.org</a><br class="">https://lists.jboss.org/mailman/listinfo/aerogear-dev</div></blockquote></div><br class=""></body></html>