Hi Tommy, On Tue, Jul 2, 2013 at 8:58 PM, Tommy McCarthy <tomccart(a)redhat.com&gt; wrote: > Hey everyone, > I'm looking to make an Android push-enabled QuickStart to demonstrate the push server on OpenShift. great! > I was initially going to implement this on the TODO application, but it looks like that will likely be removed. not necessarily. But I *think* (not 100% sure) in one of our meetings, we said that we may need a new show-case (with no longer maintaining TODO). But that maybe misunderstanding. So I am not sure on adding "Push" to the TODO app... > > Do you have any suggestions for a QuickStart that I could tackle that could be used to demonstrate the push server on OpenShift? We have a thread that currently discusses a new show-case, and topic demos etc. Perhaps that is the right source to look into as well ? Now, thinking about it. Here are a few suggestions :) Besides "pimping" a demo, what about doing some work on the "Sender SDK" ? Right now we have a Java SDK, for sending "push requests" to the PushServer. Currently we are discussing a better, more fluent, API (see [1]). I personally think a "Sender SDK" for different platforms would be nice to have: * Ruby * Node.js * PHP * Groovy The SDK(s) could be used to send Push Notification Messages from a "backend" (e.g. a Ruby/Sinatra app) to the Push-Server. Our "tutorial applications" (e.g. PushEEDemo for Android) could be used receiving the messages, submitted from the backends (e.g. Node.js app). If you would prefer something, more a long a tutorial / quickstart, how about writing a tutorial + simple demo app for JavaScript/SimplePush: https://issues.jboss.org/browse/AGPUSH-19

-Matthias [1] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Java-Sender-Messag... > > Thanks! > Tommy McCarthy > _______________________________________________ > 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 _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

On Mon, Jul 15, 2013 at 11:27 PM, Tommy McCarthy <tomccart(a)redhat.com&gt;wrote: > Hey everyone, > > After Matthias's recommendation to work on a Sender SDK or another > tutorial, I decided to tackle the Sender SDK. The proposed project is an > API written in multiple languages (currently we only have Java) to > communicate with the push server to send messages to devices/browsers. The > suggested languages are Node.js, Groovy, Ruby, and PHP. I wanted to focus > my efforts on the PHP API. > That is fine. When working on it, also make sure to follow this thread: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Java-Sender-Messag... The "java" sender is currently getting a nicer, more fluent API.

> > My internship with Red Hat is through August 30, so I will have to work > within that confine. I have taken a look at the Java client [1] and plan on > modeling it similarly to that one. Should I create a JIRA for this task, > and if so, should there be one per language? > Yes, that sounds right. File these under AGPUSH. -Matthias > > Tommy > > [1] https://github.com/aerogear/aerogear-unified-push-java-client > > ----- Original Message ----- > From: "Matthias Wessendorf" <matzew(a)apache.org&gt; > To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org&gt; > Sent: Tuesday, July 2, 2013 3:34:02 PM > Subject: Re: [aerogear-dev] QuickStart for OpenShift > > > > > On Tue, Jul 2, 2013 at 9:28 PM, Kris Borchers < kborcher(a)redhat.com > > wrote: > > > > > > On Jul 2, 2013, at 14:18, Matthias Wessendorf < matzew(a)apache.org > > wrote: > > > > > Hi Tommy, > > > On Tue, Jul 2, 2013 at 8:58 PM, Tommy McCarthy < tomccart(a)redhat.com > > wrote: > > > Hey everyone, > I'm looking to make an Android push-enabled QuickStart to demonstrate the > push server on OpenShift. > > great! > > > I was initially going to implement this on the TODO application, but it > looks like that will likely be removed. > > not necessarily. But I *think* (not 100% sure) in one of our meetings, we > said that we may need a new show-case (with no longer maintaining TODO). > But that maybe misunderstanding. > > So I am not sure on adding "Push" to the TODO app... > > > > > Do you have any suggestions for a QuickStart that I could tackle that > could be used to demonstrate the push server on OpenShift? > > We have a thread that currently discusses a new show-case, and topic > demos etc. Perhaps that is the right source to look into as well ? > > > Now, thinking about it. Here are a few suggestions :) > > Besides "pimping" a demo, what about doing some work on the "Sender SDK" ? > Right now we have a Java SDK, for sending "push requests" to the > PushServer. Currently we are discussing a better, more fluent, API (see > [1]). I personally think a "Sender SDK" for different platforms would be > nice to have: > * Ruby > * Node.js > * PHP > * Groovy > > The SDK(s) could be used to send Push Notification Messages from a > "backend" (e.g. a Ruby/Sinatra app) to the Push-Server. Our "tutorial > applications" (e.g. PushEEDemo for Android) could be used receiving the > messages, submitted from the backends (e.g. Node.js app). > > If you would prefer something, more a long a tutorial / quickstart, how > about writing a tutorial + simple demo app for JavaScript/SimplePush: > https://issues.jboss.org/browse/AGPUSH-19 > > That's probably not a good idea since I recently learned that API is > going to have to change. I've just been a little busy. ;) > > Yeah, on the Mozilla IRC channel they mentioned a JS API change. > > Tommy how you feel about the above "SDK" items before looking at > SimplePush/JavaScript bits? :-) > > > > > > > > > > -Matthias > > [1] > http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Java-Sender-Messag... > > > > > > Thanks! > Tommy McCarthy > _______________________________________________ > 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 > > > > _______________________________________________ > 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 > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > 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 > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev