<div dir="ltr">Perfect!<div><br></div><div>I think what I&#39;d do is, to pick one platform (e.g. Android) and get a feeling for a potential LiveOak SDK.</div><div><br></div><div>Our Android 2.0.0 (to continue on this platform for your POC) has been split into a few modules, which different repos:</div><div><div>* <a href="https://github.com/aerogear/aerogear-android-core">https://github.com/aerogear/aerogear-android-core</a></div><div>* <a href="https://github.com/aerogear/aerogear-android-pipe">https://github.com/aerogear/aerogear-android-pipe</a></div><div>* <a href="https://github.com/aerogear/aerogear-android-auth">https://github.com/aerogear/aerogear-android-auth</a></div><div>* <a href="https://github.com/aerogear/aerogear-android-authz">https://github.com/aerogear/aerogear-android-authz</a></div><div>* <a href="https://github.com/aerogear/aerogear-android-security">https://github.com/aerogear/aerogear-android-security</a></div><div>* <a href="https://github.com/aerogear/aerogear-android-store">https://github.com/aerogear/aerogear-android-store</a></div><div>* <a href="https://github.com/aerogear/aerogear-android-push">https://github.com/aerogear/aerogear-android-push</a></div></div><div><br></div><div>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!</div><div><br></div><div>Greetings,</div><div>Matthias</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 28, 2014 at 11:25 PM, Ken Finnigan <span dir="ltr">&lt;<a href="mailto:ken@kenfinnigan.me" target="_blank">ken@kenfinnigan.me</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Exactly what we&#39;re looking for.<div><br></div><div>Just something thin on top of AeroGear that handles any LiveOak specifics like connecting and subscribing to STOMP, and what&#39;s needed for the REST calls.</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 28, 2014 at 4:42 PM, Matthias Wessendorf <span dir="ltr">&lt;<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Ken,<div><br></div><div>a while ago, I wrote a little prototype for an iOS SDK for LiveOak:</div><div><br></div><div><a href="https://github.com/matzew/LOKIT" target="_blank">https://github.com/matzew/LOKIT</a><br></div><div><br></div><div>NOTE: Uses an old/outdated iOS library. For iOS you want our 2.x series, with swift &lt;/note&gt;</div><div><br></div><div>But to give an example:</div><div><br></div><div>That poc was (in the past) running against the chat example:</div><div><a href="https://github.com/matzew/LOKIT/blob/master/LOKitTests/LiveOakTest.m" target="_blank">https://github.com/matzew/LOKIT/blob/master/LOKitTests/LiveOakTest.m</a><br></div><div><br></div><div>Internally (similar to your web-based demo at that time), it used:</div><div>- AeroGear-iOS for http communication</div><div>- Stomp-Kit for the Stomp connection</div><div><br></div><div>All behind one thin API (was matching the JS client at that time). </div><div><br></div><div>I think that&#39;s the direction you are interested in, right? </div><div><br></div><div>If yes, we can talk about more concrete ideas ;)</div><div><br></div><div>-Matthias</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Tue, Oct 28, 2014 at 9:15 PM, Ken Finnigan <span dir="ltr">&lt;<a>ken@kenfinnigan.me</a>&gt;</span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">All,<div><br></div><div>For the next release we&#39;re looking to create some SDKs for iOS, Android, JavaScript and a Cordova plugin for use with LiveOak.</div><div><br></div><div>Our preference is to build on top of what Aerogear has already developed, or even simply use the AeroGear SDK&#39;s with a different set of connection options??</div><div><br></div><div>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&#39;re only a very thin layer on top of AeroGear&#39;s SDKs.</div><div><br></div><div>Thanks in advance!</div><span><font color="#888888"><div><br></div><div>Ken</div></font></span></div>
<br></div></div>_______________________________________________<br>
aerogear-dev mailing list<br>
<a>aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><span><font color="#888888"><br></font></span></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</font></span></div><span><font color="#888888">
<br><br>-- <br>Sent from Gmail Mobile<br>
</font></span><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div>