Hello Erik,
On Tue, Jan 21, 2014 at 10:43 AM, Erik Jan de Wit <edewit(a)redhat.com> wrote:
Hi,
Made a very simple Java version (based on hibernate) of the sync server.
I think JAX-RS is a good choice for (existing) Java EE applications.
Grizzly/Jersey was just used as an example? Or was it meant to be
'embedded' ? In that case my choice would have been undertow-resteasy:
```
UndertowJaxrsServer undertow = new UndertowJaxrsServer();
undertow.deploy(my_JAX_RS_application);
undertow.start(...);
```
Regarding the 'Car' entity: I am wondering if, on the server, something
more like the API discussed in here would be possible:
https://github.com/aerogear/aerogear.org/blob/data-sync/docs/specs/aeroge...
So, we would have a @Entity for the 'Document', where the content field
could be an 'embedded' entity/object;
It doesn’t merge so any change in a entity that is old will give a
merge
conflict. It uses the same ‘protocol’ as couch so WDYT?
Regarding the 'couch-based protocol': In theory that means our current
clients (e.g. iOS/JS) would work here too, assuming the JAX-RS server would
be following the 'document' model, right?
Cheers,
Erik Jan
https://github.com/edewit/sync-server
_______________________________________________
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