Perfect!

I think what I'd do is, to pick one platform (e.g. Android) and get a feeling for a potential LiveOak SDK.

Our Android 2.0.0 (to continue on this platform for your POC) has been split into a few modules, which different repos:

* https://github.com/aerogear/aerogear-android-core

* https://github.com/aerogear/aerogear-android-pipe

* https://github.com/aerogear/aerogear-android-auth

* https://github.com/aerogear/aerogear-android-authz

* https://github.com/aerogear/aerogear-android-security

* https://github.com/aerogear/aerogear-android-store

* https://github.com/aerogear/aerogear-android-push

If you need more details or have questions on our Android 2.0.0 series, I think new, specific mailing list threads are the way go!

Greetings,

Matthias

On Tue, Oct 28, 2014 at 11:25 PM, Ken Finnigan <ken@kenfinnigan.me> wrote:

Exactly what we're looking for.

Just something thin on top of AeroGear that handles any LiveOak specifics like connecting and subscribing to STOMP, and what's needed for the REST calls.

On Tue, Oct 28, 2014 at 4:42 PM, Matthias Wessendorf <matzew@apache.org> wrote:

Hi Ken,

a while ago, I wrote a little prototype for an iOS SDK for LiveOak:

https://github.com/matzew/LOKIT

NOTE: Uses an old/outdated iOS library. For iOS you want our 2.x series, with swift </note>

But to give an example:

That poc was (in the past) running against the chat example:

https://github.com/matzew/LOKIT/blob/master/LOKitTests/LiveOakTest.m

Internally (similar to your web-based demo at that time), it used:

- AeroGear-iOS for http communication

- Stomp-Kit for the Stomp connection

All behind one thin API (was matching the JS client at that time). 

I think that's the direction you are interested in, right? 

If yes, we can talk about more concrete ideas ;)

-Matthias

On Tue, Oct 28, 2014 at 9:15 PM, Ken Finnigan <ken@kenfinnigan.me> wrote:

All,

For the next release we're looking to create some SDKs for iOS, Android, JavaScript and a Cordova plugin for use with LiveOak.

Our preference is to build on top of what Aerogear has already developed, or even simply use the AeroGear SDK's with a different set of connection options??

As the AeroGear team are well versed in various issues of developing SDKs, I was hoping to get some advice as to the best way for us to develop ours such that they're only a very thin layer on top of AeroGear's SDKs.

Thanks in advance!

Ken

_______________________________________________
aerogear-dev mailing list
aerogear-dev@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

--
Sent from Gmail Mobile

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
aerogear-dev@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@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev