<div dir="ltr">Hey Dan,<div><br></div><div>this sounds good.</div><div><br></div><div>I expect in the mean time we should also play with prototypes and figure out what approaches fit best the needs,</div><div>and evaluate that functionally and performance-wise on sample apps.</div>
<div><br></div><div><br></div><div><br></div><div>Something what I'm missing is more comprehensive elaboration / insight in what are the target use cases and requirements on final architecture:</div><div><br></div><div>
<div><b>Requirements:</b></div><div><br></div><div>* integrate /w any general REST interface (compliant with given limitations)</div><div>** HATEOAS-compliant backend?</div><div>** generic JAX-RS?</div><div>* integrate seamlessly with LiveOak</div>
</div><div><br></div><div><b>Use cases / end-user stories:</b></div><div><br></div><div>* mobile sales client</div><div>* mobile warehouse manager</div><div>* delivery agent</div><div><br></div><div>Inspiration: <a href="https://docs.google.com/document/d/1DMacL7iwjSMPP0ytZfugpU4v0PWUK0BT6lhyaVEmlBQ/edit">https://docs.google.com/document/d/1DMacL7iwjSMPP0ytZfugpU4v0PWUK0BT6lhyaVEmlBQ/edit</a></div>
<div><br></div><div><br></div><div>I expect we target different use cases in different phases.<br></div><div>So we could indicate what use cases are valid in what phase.<br></div><div><br></div><div>Should we brainstorm this on wiki or so?</div>
<div><br></div><div><br></div><div>Cheers!</div><div><br></div><div>~ Lukas</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Aug 25, 2014 at 9:58 AM, Daniel Bevenius <span dir="ltr"><<a href="mailto:daniel.bevenius@gmail.com" target="_blank">daniel.bevenius@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">><span style="font-family:arial,sans-serif;font-size:13px">is Nov, 2014, right? </span><div><span style="font-family:arial,sans-serif;font-size:13px">Yep, sorry that should be 2015. I'll correct that. Thx</span></div>
</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On 25 August 2014 09:57, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><h3 style="font-size:1.25em;margin:1em 0px;color:rgb(226,80,39);letter-spacing:-1px;font-family:'Open Sans',sans-serif">
0.2.0 (Nov, 2015) Conflict resolvers</h3>
<div>is Nov, 2014, right? </div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Mon, Aug 25, 2014 at 9:30 AM, Daniel Bevenius <span dir="ltr"><<a href="mailto:daniel.bevenius@gmail.com" target="_blank">daniel.bevenius@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">We have been working on a roadmap for DataSync to help our planning of the features and time frames.<div>
<div>A suggestion for the roadmap can be found in this branch:</div><div><a href="https://github.com/danbev/beta.aerogear.org/tree/data-sync-rebirth-roadmap" target="_blank">https://github.com/danbev/beta.aerogear.org/tree/data-sync-rebirth-roadmap</a><br>
</div><div><br></div><div>If you don't feel like building it yourself you can try this OpenShift instance:</div><div><a href="http://diy-dbevenius.rhcloud.com/docs/planning/roadmaps/AeroGearDataSync/" target="_blank">http://diy-dbevenius.rhcloud.com/docs/planning/roadmaps/AeroGearDataSync/</a></div>
<div><br></div><div>Please note that the dates are just made up and something that we need help from each client library project to provide feedback on what is reasonable. </div><div><br></div><div>Let us know what you think and from the feedback given, either here or as PRs, we will try to break this down further and start creating JIRAs to link to the roadmap. </div>
<div><br></div><div><br></div></div></div>
<br></div></div>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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><span><font color="#888888"><br></font></span></blockquote></div><span><font color="#888888"><br>
<br clear="all"><div><br></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>
</font></span></div>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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><br></blockquote></div><br></div>
</div></div><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><br></blockquote></div><br></div>