Re: [aerogear-dev] Android - server endpoint

Hey Marko, all, So this is indeed cool stuff! A few comments: As you say, it's AppEngine-specific. While it's true that the blogger Matthias pointed to is trying to replicate the server-side with Jersey, that's very much not baked, nor is that approach sanctioned by Google as yet.

At the least we certainly want the AeroGear stuff to work on OpenShift.

It also looks kind of Eclipse-specific. Not sure if they expose command line tools for doing the codegen/etc for use with other IDEs or maven

builds - but hopefully they do. Eclipse-specificity isn't necessarily a huge problem but we definitely need to support other IDEs/workflows as well. ("right?" -- says the die-hard IntelliJ user :) ) All in all this seems to be rather a lot like what AeroGear (and Parse/Kinvey/Stackmob/etc) is trying to actually become, so perhaps it's more another competitor in the ecosystem as opposed to something we really want to use as foundation. That said, if there are useful pieces we can borrow, that'd be dandy - i.e. if we're really happy with their wire-level API and codegen tools then perhaps there'd be a way to leverage those things with a JBoss backend.

Finally, their stuff isn't public yet, so it would seem somewhat challenging to hitch to their wagon in the near term even if we wanted to.

Thoughts? Thanks, --Glen On 8/14/12 2:22 PM, Marko Strukelj wrote: > I want to share some links from Google I/O 2012 that describe current > solution from Google with respect of ease of development - how to > have a REST endpoint in support of client apps on multiple > platforms. > > One interesting solution is something they call Endpoints. It's > AppEngine-centric, but you can think of AppEngine as your server-side > wherever it's hosted. The idea is that you create your endpoint - a > REST service, annotate it with some annotations and then use tooling > to generate client library for your REST service. And you can > generate client libs in java, ObjectiveC, javascript ... > > A very nice demo of this (starts playing where the interesting part > begins): http://youtu.be/NU_wNR_UUn4?t=9m24s > > Note at 19:36 into the video (http://youtu.be/NU_wNR_UUn4?t=19m36s) a > mentioned JSON description of deployed REST service, and API > Explorer. > > API Explorer is really cool stuff - you can explore your REST service > from your browser, and interact with it. And JSON based metadata > about the service allows direct usage in javascript libraries in the > browser. > > At 22:41 into the movie (http://youtu.be/NU_wNR_UUn4?t=22m41s) there > is a demo of Google Plugin for Eclipse used to generate client side > API from a web service. > > > > There is another interesting video on the topic: > http://youtu.be/dylFNrvZ_3U?t=26m45s > > It starts a bit slowly but it's necessary to explain what a demo app > does, and then gets more interesting about 35:40 into the video > (http://youtu.be/dylFNrvZ_3U?t=35m40s). > > > Some food for thought ... > > - marko _______________________________________________ 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