Hey Dan,
this sounds good.
I expect in the mean time we should also play with prototypes and figure
out what approaches fit best the needs,
and evaluate that functionally and performance-wise on sample apps.
Something what I'm missing is more comprehensive elaboration / insight in
what are the target use cases and requirements on final architecture:
*Requirements:*
* integrate /w any general REST interface (compliant with given limitations)
** HATEOAS-compliant backend?
** generic JAX-RS?
* integrate seamlessly with LiveOak
*Use cases / end-user stories:*
* mobile sales client
* mobile warehouse manager
* delivery agent
Inspiration:
https://docs.google.com/document/d/1DMacL7iwjSMPP0ytZfugpU4v0PWUK0BT6lhya...
I expect we target different use cases in different phases.
So we could indicate what use cases are valid in what phase.
Should we brainstorm this on wiki or so?
Cheers!
~ Lukas
On Mon, Aug 25, 2014 at 9:58 AM, Daniel Bevenius <daniel.bevenius(a)gmail.com>
wrote:
>is Nov, 2014, right?
Yep, sorry that should be 2015. I'll correct that. Thx
On 25 August 2014 09:57, Matthias Wessendorf <matzew(a)apache.org> wrote:
> 0.2.0 (Nov, 2015) Conflict resolvers
> is Nov, 2014, right?
>
>
> On Mon, Aug 25, 2014 at 9:30 AM, Daniel Bevenius <
> daniel.bevenius(a)gmail.com> wrote:
>
>> We have been working on a roadmap for DataSync to help our planning of
>> the features and time frames.
>>
>> A suggestion for the roadmap can be found in this branch:
>>
>>
https://github.com/danbev/beta.aerogear.org/tree/data-sync-rebirth-roadmap
>>
>> If you don't feel like building it yourself you can try this OpenShift
>> instance:
>>
http://diy-dbevenius.rhcloud.com/docs/planning/roadmaps/AeroGearDataSync/
>>
>> 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.
>>
>> 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.
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)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(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev