Got it... the iOS bits are here:
http://www.youtube.com/watch?v=NU_wNR_UUn4&feature=player_detailpage#...
Interesting... in the demo code I still saw the 'game' is using
another iOS lib, from Google:
http://code.google.com/p/gtm-http-fetcher/
I think I need to take a look at the generated .h and .m files for iOS...
Anyway, the approach is very interesting, but it's more app specific.
It generates APIs for the particular apps, for different platforms.
Yay!
Under the cover these 'generated APIs' use some sort of (minimal) http
client library, which is - again - specific for its native platform.
For #aerogear, the initial task is coming up with the actual client
libs, for JS, iOS and Android,
Once that is somewhat done, I think it would be cool to see if the
TODO app would be build with something like this,
But... right now, I think that's a bit out of scope..
-Matthias
On Tue, Aug 14, 2012 at 8:30 PM, Matthias Wessendorf <matzew(a)apache.org> wrote:
here it goes....
http://bazinga-unit.blogspot.de/2012/08/replacing-google-cloud-endpoints-...
On Tue, Aug 14, 2012 at 8:30 PM, Matthias Wessendorf <matzew(a)apache.org> wrote:
> Hey Marko,
>
> thanks for the info!
>
> On Tue, Aug 14, 2012 at 8:22 PM, Marko Strukelj <mstrukel(a)redhat.com> 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.
>
>
> here is already a blog entry that explains how to replace w/ JAX-RS
>
>
>> And you can generate client libs in java, ObjectiveC, javascript ...
>>
>
> does one of the videos show the actual ObjC code generation ?
>
> -Matthias
>
>
>
>> 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
>
>
>
> --
> Matthias Wessendorf
>
> blog:
http://matthiaswessendorf.wordpress.com/
> sessions:
http://www.slideshare.net/mwessendorf
> twitter:
http://twitter.com/mwessendorf
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf