<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 31, 2014 at 4:39 PM, Karel Piwko <span dir="ltr"><<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Mon, 31 Mar 2014 15:25:41 +0200<br>
Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
<br>
> Hello there,<br>
><br>
> we recently had talks about creating some simplified quickstarts and<br>
> hello-word demos, related to the UnifiedPush Server and JBoss AS developers:<br>
><br>
> * Hello World (No Server Code - just client receiving push, no fancy<br>
> (complex) UI on the client, nor integrated into a Cookbook or something<br>
> that has "dependencies")<br>
> ** Cordova<br>
> ** Android<br>
><br>
> For iOS that is already there:<br>
> <a href="https://github.com/aerogear/aerogear-push-ios-demo" target="_blank">https://github.com/aerogear/aerogear-push-ios-demo</a><br>
><br>
> Yes, just usage of the "Push Registration SDKs", is the goal here: keep it<br>
> simple, since native push can be a complicated use-case all on its own and<br>
> so it will be good to make sure we cover the basics here.<br>
><br>
><br>
> Beyond the Hello-World, we wanted some different quickstarts. The "server"<br>
> components that come to mind would be:<br>
><br>
> *Secured CRUD + Push Integration (Java Sender)<br>
> ** JAX-RS + PicketLink<br>
> ** SpringMVC/Spring Security<br>
> ** JAX-RS + Apache Camel<br>
><br>
> These need to function on both JBoss AS 7.X and EAP.<br>
><br>
> Josh, from the JDF team, has already said he wants to help on the server<br>
> projects (especially the JAX-RS/PL and Spring ones). yay!<br>
> Note: Josh already has a simple backend started that is used in JDF<br>
> quickstarts that would be good to re-use to make it easier for developers<br>
> to transition from one to other.<br>
><br>
><br>
> The goal would be the SERVER acts same to outside (identical REST<br>
> endpoints, difference is only an impl. detail (e.g. JavaEE vs. Spring vs.<br>
> Camel))<br>
><br>
> For these different servers, there would be mobile apps needed:<br>
> * Android<br>
> * Cordova<br>
> * iOS<br>
<br>
</div></div>I'm not sure if I got that. You mean extra 3 apps per each supported backed?<br>
Making it 9 additional apps to test and maintain?<br></blockquote><div><br></div><div><br></div><div>No: total of 3 server apps and 3 client apps</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Should not the client be the same no matter have backend is set up?<br>
<div class="im HOEnZb"><br>
><br>
><br>
> The idea would be to keep them simple and straightforward as well, e.g. for<br>
> iOS that means plain usage of NSURLConnection / NSURLSession. But for the<br>
> "push registration" of the client,<br>
> the iOS-push SDK would be used (same/similar would apply to Cordova or<br>
> Android). Similar to the above 'Hello World', the quickstarts are going to<br>
> be focused only on Push functionality, so for these we would leave out<br>
> pipes and such until later versions.<br>
><br>
><br>
> I will be creating Epics and subtasks in JIRA for this.<br>
><br>
> For the location of all these projects, I had this "uber repo" location in<br>
> mind:<br>
> * <a href="https://github.com/aerogear/aerogear-push-helloworld" target="_blank">https://github.com/aerogear/aerogear-push-helloworld</a><br>
> * <a href="https://github.com/aerogear/aerogear-push-quickstarts" target="_blank">https://github.com/aerogear/aerogear-push-quickstarts</a><br>
><br>
> Greetings,<br>
> Matthias<br>
><br>
><br>
><br>
<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<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>
</div></div></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></div>