From idel.pivnitskiy at gmail.com Mon Apr 4 05:50:57 2016 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Mon, 4 Apr 2016 12:50:57 +0300 Subject: [aerogear-dev] Big Data tools with AeroGear Message-ID: Hi all! As you know from my proposal for GSoC, I study on a Master's program "Big Data Systems". I need to implement any project with Apache Spark or something similar. Do you have any ideas, how it can be integrated with UPS or other AeroGear projects? I think about connector to Spark Streaming API to provide real-time analytic. Is it reasonable? Does anyone use UPS in high load projects? FeedHenry? Or it could be reasonable when we will integrate WebPush Server. Any thoughts/other ideas? Thanks! Idel Pivnitskiy -- Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160404/e93cc5f9/attachment.html From hrupp at redhat.com Mon Apr 4 08:37:38 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Mon, 04 Apr 2016 14:37:38 +0200 Subject: [aerogear-dev] Big Data tools with AeroGear In-Reply-To: References: Message-ID: <963F68A8-3CB4-4A91-8955-3F58B71BBD81@redhat.com> On 4 Apr 2016, at 11:50, Idel Pivnitskiy wrote: > I think about connector to Spark Streaming API to provide real-time > analytic. Is it reasonable? Does anyone use UPS in high While not related to AeroGear (directly), Hawkular does some predictive analytics on measurement data. We have an intern / university student working on this. Not on spark but some "homegrown" code. Which may also be of interest. From matzew at apache.org Tue Apr 5 05:10:04 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 5 Apr 2016 11:10:04 +0200 Subject: [aerogear-dev] UPS: Staging on 1.2.0-alpha.1 Message-ID: Hi, this is the attempt to release a first alpha of the 1.2.0 series! The release is basically all the fixes from 1.1.2 as well, as some larger changes and improvements: * Support for WildFly-10 and EAP7 (no longer supporting older versions) * Update to a more recent Keycloak version (1.7.1) * Java-8 based build * improvements on the internal JMS system: ** preventing Tokenloader from memory issues ** APNs cache improvements All details can be found on the JIRA: https://issues.jboss.org/projects/AGPUSH/versions/12329905 The staging repo is located here: https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7977/ I'd like to release it later this week. If you have time, please test this new version on WildFly10 Greetings, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160405/e8ed2e6f/attachment.html From matzew at apache.org Tue Apr 5 05:21:27 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 5 Apr 2016 11:21:27 +0200 Subject: [aerogear-dev] UPS: Staging on 1.2.0-alpha.1 In-Reply-To: References: Message-ID: Note, besides the DB CLI script, we also now have some setup for JMS: https://github.com/aerogear/aerogear.org/blob/master/docs/unifiedpush/ups_userguide/server-installation.asciidoc#configure-jms-destinations-for-the-unifiedpush On Tue, Apr 5, 2016 at 11:10 AM, Matthias Wessendorf wrote: > Hi, > > this is the attempt to release a first alpha of the 1.2.0 series! The > release is basically all the fixes from 1.1.2 as well, as some larger > changes and improvements: > * Support for WildFly-10 and EAP7 (no longer supporting older versions) > * Update to a more recent Keycloak version (1.7.1) > * Java-8 based build > * improvements on the internal JMS system: > ** preventing Tokenloader from memory issues > ** APNs cache improvements > > All details can be found on the JIRA: > https://issues.jboss.org/projects/AGPUSH/versions/12329905 > > > The staging repo is located here: > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7977/ > > I'd like to release it later this week. If you have time, please test this > new version on WildFly10 > > > Greetings, > Matthias > > > -- > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160405/99cb0ee1/attachment.html From matzew at apache.org Wed Apr 6 11:57:19 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 6 Apr 2016 17:57:19 +0200 Subject: [aerogear-dev] UPS: Staging on 1.2.0-alpha.1 In-Reply-To: References: Message-ID: clicked the btn and will update the docker and Openshift bits later this week -M On Tue, Apr 5, 2016 at 11:21 AM, Matthias Wessendorf wrote: > Note, besides the DB CLI script, we also now have some setup for JMS: > > https://github.com/aerogear/aerogear.org/blob/master/docs/unifiedpush/ups_userguide/server-installation.asciidoc#configure-jms-destinations-for-the-unifiedpush > > > > On Tue, Apr 5, 2016 at 11:10 AM, Matthias Wessendorf > wrote: > >> Hi, >> >> this is the attempt to release a first alpha of the 1.2.0 series! The >> release is basically all the fixes from 1.1.2 as well, as some larger >> changes and improvements: >> * Support for WildFly-10 and EAP7 (no longer supporting older versions) >> * Update to a more recent Keycloak version (1.7.1) >> * Java-8 based build >> * improvements on the internal JMS system: >> ** preventing Tokenloader from memory issues >> ** APNs cache improvements >> >> All details can be found on the JIRA: >> https://issues.jboss.org/projects/AGPUSH/versions/12329905 >> >> >> The staging repo is located here: >> >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7977/ >> >> I'd like to release it later this week. If you have time, please test >> this new version on WildFly10 >> >> >> Greetings, >> Matthias >> >> >> -- >> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160406/80eb568a/attachment.html From matzew at apache.org Thu Apr 7 07:27:41 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 7 Apr 2016 13:27:41 +0200 Subject: [aerogear-dev] Titanium and UPS Message-ID: Hi all, I am very excited to see that our friends at Napp created another nice lib for the UPS, supporting Titanium: https://github.com/Napp/AeroGear-Push-Titanium Cheers! Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160407/de87c752/attachment.html From matzew at apache.org Fri Apr 8 11:28:45 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 8 Apr 2016 17:28:45 +0200 Subject: [aerogear-dev] GCM Device Token not accepted In-Reply-To: References: <1458222270230-12403.post@n5.nabble.com>

Message-ID: Hi, did you managed to get it working? I am wondering if it was a temporary issue for you - looks like for Summers it worked On Wed, Mar 30, 2016 at 5:14 PM, Summers Pittman wrote: > I know "Works on my machine" is a bad response, but well, works on my > machine* > > The caveats are I am using UPS 1.1.2 and AGDroid-push 3.0.0-SNAPSHOT. As > far as I know AGDroid 2.2.2 does not use Instance ID. > > I've uploaded some screen shots here : http://imgur.com/a/eKF4F > > Can you provide some more details? What versions of things are you > using? Can you gist your source code, etc. > > > > On Wed, Mar 23, 2016 at 8:34 PM, Matthias Wessendorf > wrote: > >> >> >> On Thu, Mar 24, 2016 at 1:00 AM, Matthias Wessendorf >> wrote: >> >>> Hello, >>> >>> sorry for the late reply, but the mail got stuck in my moderation queue >>> :-( >>> >>> >>> On Thu, Mar 17, 2016 at 2:44 PM, cel wrote: >>> >>>> The new device Token returned by the new GCM - API for Android (using >>>> InstanceId.getToken instead of gcm.register(context), which is >>>> deprecated) >>>> >>> >>> For that we have a ticket, but weren't able to get to it: >>> https://issues.jboss.org/browse/AGDROID-427 >>> >>> >>>> is not accepted by the Aerogear server. The format of the >>>> InstanceId.getToken is different. >>>> Example: >>>> Beginnning of gcm.register - Token : >>>> APA91bGdSq3-OKaDV_pyvunTZpnD_LKb6OrxIk7... >>>> Beginning of InstanceId.getToken : >>>> eArreQ7017w:APA91bFe5lTYzEoNSivfPYaID... >>>> So if I try to register with the InstanceId.getToken using the Restful >>>> interface "/registry/device" the Http response of the aerogear server >>>> is: >>>> "200 OK", but I still cannot find it in the installations. Consequently >>>> no >>>> >>> >> I think the weird part is, that it's returning 200 to the Android device, >> which means it was accepted, >> but something else went wrong, while sending. >> >> Any more logs? Or can you increase logging on the UPS? >> https://aerogear.org/docs/unifiedpush/ups_userguide/index/#debugging >> >> >> >>> push notifications from aerogear can be sent to that device. Is this a >>>> Bug? >>>> Has this been fixed in newer versions? >>>> >>> >>> yes, that's a bug - looks like the token format changed w/ InstanceId, >>> and our 'validator' needs to be updated. >>> >>> Thanks for reporting, I have filed a JIRA and we will be looking at it: >>> https://jira.jboss.org/browse/AGPUSH-1600 >>> >>> -Matthias >>> >>> >>> >>> >>>> >>>> >>>> >>>> >>>> -- >>>> View this message in context: >>>> http://aerogear-dev.1069024.n5.nabble.com/GCM-Device-Token-not-accepted-tp12403.html >>>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160408/4b0adfa7/attachment-0001.html From matzew at apache.org Fri Apr 8 11:42:25 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 8 Apr 2016 17:42:25 +0200 Subject: [aerogear-dev] GCM Device Token not accepted In-Reply-To: References: <1458222270230-12403.post@n5.nabble.com>

Message-ID: Hi, I think you are using an older version of the UPS. For 1.1.0, we actually did add support for the GCM-3 token format (InstanceID). Can you tell us the version number ? On Fri, Apr 8, 2016 at 5:28 PM, Matthias Wessendorf wrote: > Hi, > > did you managed to get it working? I am wondering if it was a temporary > issue for you - looks like for Summers it worked > > On Wed, Mar 30, 2016 at 5:14 PM, Summers Pittman > wrote: > >> I know "Works on my machine" is a bad response, but well, works on my >> machine* >> >> The caveats are I am using UPS 1.1.2 and AGDroid-push 3.0.0-SNAPSHOT. As >> far as I know AGDroid 2.2.2 does not use Instance ID. >> >> I've uploaded some screen shots here : http://imgur.com/a/eKF4F >> >> Can you provide some more details? What versions of things are you >> using? Can you gist your source code, etc. >> >> >> >> On Wed, Mar 23, 2016 at 8:34 PM, Matthias Wessendorf >> wrote: >> >>> >>> >>> On Thu, Mar 24, 2016 at 1:00 AM, Matthias Wessendorf >>> wrote: >>> >>>> Hello, >>>> >>>> sorry for the late reply, but the mail got stuck in my moderation queue >>>> :-( >>>> >>>> >>>> On Thu, Mar 17, 2016 at 2:44 PM, cel wrote: >>>> >>>>> The new device Token returned by the new GCM - API for Android (using >>>>> InstanceId.getToken instead of gcm.register(context), which is >>>>> deprecated) >>>>> >>>> >>>> For that we have a ticket, but weren't able to get to it: >>>> https://issues.jboss.org/browse/AGDROID-427 >>>> >>>> >>>>> is not accepted by the Aerogear server. The format of the >>>>> InstanceId.getToken is different. >>>>> Example: >>>>> Beginnning of gcm.register - Token : >>>>> APA91bGdSq3-OKaDV_pyvunTZpnD_LKb6OrxIk7... >>>>> Beginning of InstanceId.getToken : >>>>> eArreQ7017w:APA91bFe5lTYzEoNSivfPYaID... >>>>> So if I try to register with the InstanceId.getToken using the Restful >>>>> interface "/registry/device" the Http response of the aerogear server >>>>> is: >>>>> "200 OK", but I still cannot find it in the installations. >>>>> Consequently no >>>>> >>>> >>> I think the weird part is, that it's returning 200 to the Android >>> device, which means it was accepted, >>> but something else went wrong, while sending. >>> >>> Any more logs? Or can you increase logging on the UPS? >>> https://aerogear.org/docs/unifiedpush/ups_userguide/index/#debugging >>> >>> >>> >>>> push notifications from aerogear can be sent to that device. Is this a >>>>> Bug? >>>>> Has this been fixed in newer versions? >>>>> >>>> >>>> yes, that's a bug - looks like the token format changed w/ InstanceId, >>>> and our 'validator' needs to be updated. >>>> >>>> Thanks for reporting, I have filed a JIRA and we will be looking at it: >>>> https://jira.jboss.org/browse/AGPUSH-1600 >>>> >>>> -Matthias >>>> >>>> >>>> >>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> View this message in context: >>>>> http://aerogear-dev.1069024.n5.nabble.com/GCM-Device-Token-not-accepted-tp12403.html >>>>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev at 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 >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160408/e291ffe6/attachment.html From matzew at apache.org Fri Apr 8 11:45:37 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 8 Apr 2016 17:45:37 +0200 Subject: [aerogear-dev] GCM Device Token not accepted In-Reply-To: References: <1458222270230-12403.post@n5.nabble.com>

Message-ID: here is the commit, btw: https://github.com/aerogear/aerogear-unifiedpush-server/commit/fa74eea6a183d852fb26773bb1b62cf9016c9157 On Fri, Apr 8, 2016 at 5:42 PM, Matthias Wessendorf wrote: > Hi, > > I think you are using an older version of the UPS. > > For 1.1.0, we actually did add support for the GCM-3 token format > (InstanceID). > > Can you tell us the version number ? > > On Fri, Apr 8, 2016 at 5:28 PM, Matthias Wessendorf > wrote: > >> Hi, >> >> did you managed to get it working? I am wondering if it was a temporary >> issue for you - looks like for Summers it worked >> >> On Wed, Mar 30, 2016 at 5:14 PM, Summers Pittman >> wrote: >> >>> I know "Works on my machine" is a bad response, but well, works on my >>> machine* >>> >>> The caveats are I am using UPS 1.1.2 and AGDroid-push 3.0.0-SNAPSHOT. >>> As far as I know AGDroid 2.2.2 does not use Instance ID. >>> >>> I've uploaded some screen shots here : http://imgur.com/a/eKF4F >>> >>> Can you provide some more details? What versions of things are you >>> using? Can you gist your source code, etc. >>> >>> >>> >>> On Wed, Mar 23, 2016 at 8:34 PM, Matthias Wessendorf >>> wrote: >>> >>>> >>>> >>>> On Thu, Mar 24, 2016 at 1:00 AM, Matthias Wessendorf >>> > wrote: >>>> >>>>> Hello, >>>>> >>>>> sorry for the late reply, but the mail got stuck in my moderation >>>>> queue :-( >>>>> >>>>> >>>>> On Thu, Mar 17, 2016 at 2:44 PM, cel wrote: >>>>> >>>>>> The new device Token returned by the new GCM - API for Android (using >>>>>> InstanceId.getToken instead of gcm.register(context), which is >>>>>> deprecated) >>>>>> >>>>> >>>>> For that we have a ticket, but weren't able to get to it: >>>>> https://issues.jboss.org/browse/AGDROID-427 >>>>> >>>>> >>>>>> is not accepted by the Aerogear server. The format of the >>>>>> InstanceId.getToken is different. >>>>>> Example: >>>>>> Beginnning of gcm.register - Token : >>>>>> APA91bGdSq3-OKaDV_pyvunTZpnD_LKb6OrxIk7... >>>>>> Beginning of InstanceId.getToken : >>>>>> eArreQ7017w:APA91bFe5lTYzEoNSivfPYaID... >>>>>> So if I try to register with the InstanceId.getToken using the >>>>>> Restful >>>>>> interface "/registry/device" the Http response of the aerogear server >>>>>> is: >>>>>> "200 OK", but I still cannot find it in the installations. >>>>>> Consequently no >>>>>> >>>>> >>>> I think the weird part is, that it's returning 200 to the Android >>>> device, which means it was accepted, >>>> but something else went wrong, while sending. >>>> >>>> Any more logs? Or can you increase logging on the UPS? >>>> https://aerogear.org/docs/unifiedpush/ups_userguide/index/#debugging >>>> >>>> >>>> >>>>> push notifications from aerogear can be sent to that device. Is this a >>>>>> Bug? >>>>>> Has this been fixed in newer versions? >>>>>> >>>>> >>>>> yes, that's a bug - looks like the token format changed w/ InstanceId, >>>>> and our 'validator' needs to be updated. >>>>> >>>>> Thanks for reporting, I have filed a JIRA and we will be looking at it: >>>>> https://jira.jboss.org/browse/AGPUSH-1600 >>>>> >>>>> -Matthias >>>>> >>>>> >>>>> >>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://aerogear-dev.1069024.n5.nabble.com/GCM-Device-Token-not-accepted-tp12403.html >>>>>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160408/78bff58b/attachment-0001.html From sharathmk99 at gmail.com Sat Apr 9 15:29:33 2016 From: sharathmk99 at gmail.com (Sharath MK) Date: Sun, 10 Apr 2016 00:59:33 +0530 Subject: [aerogear-dev] How to add Custom Push Notification Service. Message-ID: Hi, I was building a MQTT based push notification. I want to use this platform to host MQTT bar push notification service also. Can you please tell me how to integrate my push service to UPC server. So that from ui one can select and send. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160410/a4171a6b/attachment.html From idel.pivnitskiy at gmail.com Tue Apr 12 07:46:59 2016 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Tue, 12 Apr 2016 14:46:59 +0300 Subject: [aerogear-dev] JDK7 support for Pushy library Message-ID: Hi! A few weeks ago we discussed JDK version requirements for Pushy library. Matthias had sent a PR [1] and it didn't work. I analyzed the problem and find a cause: yes, clean Netty's codec-http2 doesn't requires JDK8. But JDK 7 SSL provider does not support the cipher suites recommended by the HTTP2 RFC [2]. We can use JDK 7 only with native OpenSSL as the default TLS provider. Jon Chambers added JDK 7 build to Travis yesterday [3]. I've added OpenJDK 7 too today [4]. [1] https://github.com/relayrides/pushy/pull/252 [2] http://netty.io/wiki/requirements-for-4.x.html#jdk-ciphers [3] https://github.com/relayrides/pushy/pull/268 [4] https://github.com/relayrides/pushy/pull/269 Best regards, Idel Pivnitskiy -- E-mail: idel.pivnitskiy at gmail.com Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160412/359c7464/attachment.html From matzew at apache.org Tue Apr 12 07:55:26 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 12 Apr 2016 13:55:26 +0200 Subject: [aerogear-dev] JDK7 support for Pushy library In-Reply-To: References: Message-ID: Thanks for the heads up, Idel. -Matthias On Tue, Apr 12, 2016 at 1:46 PM, Idel Pivnitskiy wrote: > Hi! > > A few weeks ago we discussed JDK version requirements for Pushy library. > Matthias had sent a PR [1] and it didn't work. > > I analyzed the problem and find a cause: yes, clean Netty's codec-http2 > doesn't requires JDK8. But JDK 7 SSL provider does not support the cipher > suites recommended by the HTTP2 RFC [2]. We can use JDK 7 only with > native OpenSSL as the default TLS provider. > Jon Chambers added JDK 7 build to Travis yesterday [3]. I've added OpenJDK > 7 too today [4]. > > [1] https://github.com/relayrides/pushy/pull/252 > [2] http://netty.io/wiki/requirements-for-4.x.html#jdk-ciphers > [3] https://github.com/relayrides/pushy/pull/268 > [4] https://github.com/relayrides/pushy/pull/269 > > Best regards, > Idel Pivnitskiy > -- > E-mail: idel.pivnitskiy at gmail.com > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160412/a62f2d2b/attachment.html From scm.blanc at gmail.com Tue Apr 12 08:24:20 2016 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 12 Apr 2016 14:24:20 +0200 Subject: [aerogear-dev] How to add Custom Push Notification Service. In-Reply-To: References: Message-ID: Hi, Some time ago, I wrote a document that describes all the steps that are needed to implement a custom platform in UPS, everything is pretty still up to date, except the UI that has change a lot but, still it should give you good pointers : https://gist.github.com/sebastienblanc/9615439c67968ecb92da Seb On Sat, Apr 9, 2016 at 9:29 PM, Sharath MK wrote: > Hi, > > I was building a MQTT based push notification. I want to use this platform > to host MQTT bar push notification service also. Can you please tell me how > to integrate my push service to UPC server. So that from ui one can select > and send. > > Thanks > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160412/013ebf08/attachment.html From idel.pivnitskiy at gmail.com Tue Apr 12 08:47:20 2016 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Tue, 12 Apr 2016 15:47:20 +0300 Subject: [aerogear-dev] Big Data tools with AeroGear In-Reply-To: <963F68A8-3CB4-4A91-8955-3F58B71BBD81@redhat.com> References: <963F68A8-3CB4-4A91-8955-3F58B71BBD81@redhat.com> Message-ID: Thank you, Heiko! The task should be more practical (like implement a connector to Spark Streaming API) and quick to solve for this time, not a deep analytic research. Just to try some tools in action :) But yes, Hawkular has much more possible task for data analysis. Will write to its mailing list if I have some tasks/ideas. Best regards, Idel Pivnitskiy -- Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy On Mon, Apr 4, 2016 at 3:37 PM, Heiko W.Rupp wrote: > On 4 Apr 2016, at 11:50, Idel Pivnitskiy wrote: > > > I think about connector to Spark Streaming API to provide real-time > > analytic. Is it reasonable? Does anyone use UPS in high > > While not related to AeroGear (directly), Hawkular does > some predictive analytics on measurement data. We have > an intern / university student working on this. Not on > spark but some "homegrown" code. Which may also be > of interest. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160412/34adb386/attachment.html From idel.pivnitskiy at gmail.com Thu Apr 14 05:29:29 2016 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Thu, 14 Apr 2016 12:29:29 +0300 Subject: [aerogear-dev] @requestheader javadoc tag for Miredot Message-ID: Hi, Miredot team accepted our request to add a new custom javadoc tag "@requestheader", as we discussed later [1], and added it to their backlog. So, let's wait a new release :) Also, they announced Miredot 2.0-RC with a lot of new features [2]. I will try to update to the latest version. [1] https://github.com/matzew/aerogear-unifiedpush-server/pull/11#discussion_r55151537 [2] http://miredot.com/docs/release-notes/ Best regards, Idel Pivnitskiy -- Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160414/18ee92e1/attachment-0001.html From matzew at apache.org Thu Apr 14 05:33:27 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 14 Apr 2016 11:33:27 +0200 Subject: [aerogear-dev] @requestheader javadoc tag for Miredot In-Reply-To: References: Message-ID: Awesome! :) Thanks for driving this On Thu, Apr 14, 2016 at 11:29 AM, Idel Pivnitskiy wrote: > Hi, > > Miredot team accepted our request to add a new custom javadoc tag > "@requestheader", as we discussed later [1], and added it to their backlog. > So, let's wait a new release :) > Also, they announced Miredot 2.0-RC with a lot of new features [2]. I will > try to update to the latest version. > > [1] > https://github.com/matzew/aerogear-unifiedpush-server/pull/11#discussion_r55151537 > [2] http://miredot.com/docs/release-notes/ > > Best regards, > Idel Pivnitskiy > -- > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160414/1cb176ae/attachment.html From supittma at redhat.com Mon Apr 18 13:01:31 2016 From: supittma at redhat.com (Summers Pittman) Date: Mon, 18 Apr 2016 13:01:31 -0400 Subject: [aerogear-dev] Consuming Google-Services.json Message-ID: See JIRA : https://issues.jboss.org/browse/AGDROID-473 Background : Currently we have a developer manually enter the Google Project ID to enable push messages in their application. However, this approach is considered "legacy" from Google's POV and they are encouraging consuming the Google-services.json file. There are two ways we can consume this file. The first is to parse it manually and extract the key "project_info/project_number"[1]. The second is to have the developer add the google services plugin to their Gradle projects and then we can consume the key from the resources with the field "R.string.gcm_defaultSenderId". I would prefer to parse the file manually. It make our code less reliant on Google's tools and it allows our users to choose if they will use Google's plug in for its other features. However, Google's plugin may provide extra features or validation which may be useful in the future. Wdyt? Summers 1: This is a documented value described in this section : https://developers.google.com/android/guides/google-services-plugin#processing_the_json_file -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160418/19115ac8/attachment.html From matzew at apache.org Mon Apr 18 14:25:28 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 18 Apr 2016 20:25:28 +0200 Subject: [aerogear-dev] Consuming Google-Services.json In-Reply-To: References: Message-ID: On Mon, Apr 18, 2016 at 7:01 PM, Summers Pittman wrote: > See JIRA : https://issues.jboss.org/browse/AGDROID-473 > Played w/ that file today as well :-) > > Background : Currently we have a developer manually enter the Google > Project ID to enable push messages in their application. However, this > approach is considered "legacy" from Google's POV and they are encouraging > consuming the Google-services.json file. > > There are two ways we can consume this file. The first is to parse it > manually and extract the key "project_info/project_number"[1]. > That's sounds most safe thing, and it's safe, according to Google :) In case the "project_number" is not present (e.g. dev is 'smart' and edits file), let's have a proper error and call it a day :-) > The second is to have the developer add the google services plugin to > their Gradle projects and then we can consume the key from the resources > with the field "R.string.gcm_defaultSenderId". > > I would prefer to parse the file manually. It make our code less reliant > on Google's tools and it allows our users to choose if they will use > Google's plug in for its other features. > Yeah, I feel same, might be also a bit odd to rely on a plugin, just for this... > However, Google's plugin may provide extra features or validation which > may be useful in the future. > Sure, comes time, we can see :) > > > Wdyt? > > Summers > > 1: This is a documented value described in this section : > https://developers.google.com/android/guides/google-services-plugin#processing_the_json_file > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160418/f4db056d/attachment.html From matzew at apache.org Wed Apr 20 06:19:57 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 20 Apr 2016 12:19:57 +0200 Subject: [aerogear-dev] GCM3: InstanceID tokens versus 'old' tokens Message-ID: Hi, the format for tokens received from InstanceID API have a slightly different format: https://github.com/aerogear/aerogear-unifiedpush-server/commit/fa74eea6a183d852fb26773bb1b62cf9016c9157 It's basically (prefix_string : RegistrationID). Now, in order to be able to subscribe on a topic is it _really_ required to have a 'new' InstanceID token ? I could not find a _clear_ statement I am asking because I'm working on the server hook to send topic request. If the answer yes, only InstanceID tokens can subscribe, we need a little switch on the server (not a show stopper): 1) send /topics/{something} (should not affect 'old' tokens_ 2) fallback: find tokens w/o the ':', so we can fallback to pure registration Id for "non-Instance ID " tokens Thanks, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160420/ace0958b/attachment.html From matzew at apache.org Wed Apr 20 07:23:08 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 20 Apr 2016 13:23:08 +0200 Subject: [aerogear-dev] GCM3: InstanceID tokens versus 'old' tokens In-Reply-To: References: Message-ID: On Wed, Apr 20, 2016 at 12:19 PM, Matthias Wessendorf wrote: > Hi, > > the format for tokens received from InstanceID API have a slightly > different format: > > https://github.com/aerogear/aerogear-unifiedpush-server/commit/fa74eea6a183d852fb26773bb1b62cf9016c9157 > > It's basically (prefix_string : RegistrationID). > > Now, in order to be able to subscribe on a topic is it _really_ required > to have a 'new' InstanceID token ? I could not find a _clear_ statement > looks like InstanceID tokens are required: https://developers.google.com/android/reference/com/google/android/gms/gcm/GcmPubSub#public-methods But, on the other hand it does not mention that GCM.register() tokens are not allowed :-) > > I am asking because I'm working on the server hook to send topic request. > > If the answer yes, only InstanceID tokens can subscribe, we need a little > switch on the server (not a show stopper): > 1) send /topics/{something} (should not affect 'old' tokens_ > 2) fallback: find tokens w/o the ':', so we can fallback to pure > registration Id for "non-Instance ID " tokens > > > Thanks, > Matthias > > -- > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160420/28da53e1/attachment-0001.html From matzew at apache.org Wed Apr 20 07:33:55 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 20 Apr 2016 13:33:55 +0200 Subject: [aerogear-dev] GCM3: InstanceID tokens versus 'old' tokens In-Reply-To: References: Message-ID: Even if they were allowed... Apps, with older AGDroid SDKs aren't able to subscribe. That means if the UPS server updates, they all would receive no message :-) Therefore that look up for 'old' tokens is generally needed On Wed, Apr 20, 2016 at 1:23 PM, Matthias Wessendorf wrote: > > > On Wed, Apr 20, 2016 at 12:19 PM, Matthias Wessendorf > wrote: > >> Hi, >> >> the format for tokens received from InstanceID API have a slightly >> different format: >> >> https://github.com/aerogear/aerogear-unifiedpush-server/commit/fa74eea6a183d852fb26773bb1b62cf9016c9157 >> >> It's basically (prefix_string : RegistrationID). >> >> Now, in order to be able to subscribe on a topic is it _really_ required >> to have a 'new' InstanceID token ? I could not find a _clear_ statement >> > > looks like InstanceID tokens are required: > > https://developers.google.com/android/reference/com/google/android/gms/gcm/GcmPubSub#public-methods > > But, on the other hand it does not mention that GCM.register() tokens are > not allowed :-) > > >> >> I am asking because I'm working on the server hook to send topic request. >> >> If the answer yes, only InstanceID tokens can subscribe, we need a little >> switch on the server (not a show stopper): >> 1) send /topics/{something} (should not affect 'old' tokens_ >> 2) fallback: find tokens w/o the ':', so we can fallback to pure >> registration Id for "non-Instance ID " tokens >> >> >> Thanks, >> Matthias >> >> -- >> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160420/3de5c187/attachment.html From supittma at redhat.com Wed Apr 20 08:42:24 2016 From: supittma at redhat.com (Summers Pittman) Date: Wed, 20 Apr 2016 08:42:24 -0400 Subject: [aerogear-dev] GCM3: InstanceID tokens versus 'old' tokens In-Reply-To: References: Message-ID: One of the things to consider is that applications re-register each time they load. So an app can move from being registered with a GCM.register token to being registered with a InstanceID token. I think that instanceID tokens have ":"'s and GCM.register tokens do not. We should probably make a contrived scenario where an app registered and then changes to InstanceID to see what happens. It SHOULDN'T get double messages because the app update relaunch step should break the old gcm token. But we need to test it. On Wed, Apr 20, 2016 at 7:33 AM, Matthias Wessendorf wrote: > Even if they were allowed... Apps, with older AGDroid SDKs aren't able to > subscribe. That means if the UPS server updates, they all would receive no > message :-) > > Therefore that look up for 'old' tokens is generally needed > > On Wed, Apr 20, 2016 at 1:23 PM, Matthias Wessendorf > wrote: > >> >> >> On Wed, Apr 20, 2016 at 12:19 PM, Matthias Wessendorf >> wrote: >> >>> Hi, >>> >>> the format for tokens received from InstanceID API have a slightly >>> different format: >>> >>> https://github.com/aerogear/aerogear-unifiedpush-server/commit/fa74eea6a183d852fb26773bb1b62cf9016c9157 >>> >>> It's basically (prefix_string : RegistrationID). >>> >>> Now, in order to be able to subscribe on a topic is it _really_ required >>> to have a 'new' InstanceID token ? I could not find a _clear_ statement >>> >> >> looks like InstanceID tokens are required: >> >> https://developers.google.com/android/reference/com/google/android/gms/gcm/GcmPubSub#public-methods >> >> But, on the other hand it does not mention that GCM.register() tokens are >> not allowed :-) >> >> >>> >>> I am asking because I'm working on the server hook to send topic request. >>> >>> If the answer yes, only InstanceID tokens can subscribe, we need a >>> little switch on the server (not a show stopper): >>> 1) send /topics/{something} (should not affect 'old' tokens_ >>> 2) fallback: find tokens w/o the ':', so we can fallback to pure >>> registration Id for "non-Instance ID " tokens >>> >>> >>> Thanks, >>> Matthias >>> >>> -- >>> 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160420/49c1a2ec/attachment.html From matzew at apache.org Wed Apr 20 08:52:40 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 20 Apr 2016 14:52:40 +0200 Subject: [aerogear-dev] GCM3: InstanceID tokens versus 'old' tokens In-Reply-To: References:

Message-ID: On Wed, Apr 20, 2016 at 2:42 PM, Summers Pittman wrote: > One of the things to consider is that applications re-register each time > they load. > right > So an app can move from being registered with a GCM.register token to > being registered with a InstanceID token. > right, but until than ;-) > > I think that instanceID tokens have ":"'s and GCM.register tokens do not. > right, > > We should probably make a contrived scenario where an app registered and > then changes to InstanceID to see what happens. > I guess, it will get a token, following the new format. > It SHOULDN'T get double messages because the app update relaunch step > should break the old gcm token. But we need to test it. > I think for apps that (for what ever reason) not upgrade to newest AGDroid SDK, we need to use the old way of pushing: query all tokens that do NOT have a : inside -M > > On Wed, Apr 20, 2016 at 7:33 AM, Matthias Wessendorf > wrote: > >> Even if they were allowed... Apps, with older AGDroid SDKs aren't able to >> subscribe. That means if the UPS server updates, they all would receive no >> message :-) >> >> Therefore that look up for 'old' tokens is generally needed >> >> On Wed, Apr 20, 2016 at 1:23 PM, Matthias Wessendorf >> wrote: >> >>> >>> >>> On Wed, Apr 20, 2016 at 12:19 PM, Matthias Wessendorf >> > wrote: >>> >>>> Hi, >>>> >>>> the format for tokens received from InstanceID API have a slightly >>>> different format: >>>> >>>> https://github.com/aerogear/aerogear-unifiedpush-server/commit/fa74eea6a183d852fb26773bb1b62cf9016c9157 >>>> >>>> It's basically (prefix_string : RegistrationID). >>>> >>>> Now, in order to be able to subscribe on a topic is it _really_ >>>> required to have a 'new' InstanceID token ? I could not find a _clear_ >>>> statement >>>> >>> >>> looks like InstanceID tokens are required: >>> >>> https://developers.google.com/android/reference/com/google/android/gms/gcm/GcmPubSub#public-methods >>> >>> But, on the other hand it does not mention that GCM.register() tokens >>> are not allowed :-) >>> >>> >>>> >>>> I am asking because I'm working on the server hook to send topic >>>> request. >>>> >>>> If the answer yes, only InstanceID tokens can subscribe, we need a >>>> little switch on the server (not a show stopper): >>>> 1) send /topics/{something} (should not affect 'old' tokens_ >>>> 2) fallback: find tokens w/o the ':', so we can fallback to pure >>>> registration Id for "non-Instance ID " tokens >>>> >>>> >>>> Thanks, >>>> Matthias >>>> >>>> -- >>>> 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 >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160420/d4161a06/attachment-0001.html From arnob at get-it-live.com Wed Apr 20 20:10:42 2016 From: arnob at get-it-live.com (Arnob Mahmud) Date: Thu, 21 Apr 2016 02:10:42 +0200 Subject: [aerogear-dev] Facing a problem during using AeroGear OTP Cordova plugin!! Message-ID: <000501d19b62$3fd578b0$bf806a10$@get-it-live.com> Hello, Hi, I am new in using this kind of features, Well I am facing a problem which I can?t solve, on testing purpose I have created a black ionic angularjs framework based mobile application where I am using AeroGear OTP Cordova plugin and when I click the OTP button for scan I got an alert message saying ?Sorry, the Android camera encountered a problem. You may need to restart the device.? And I found no good documentation about it so far!! I am stuck on it totally now and I am in a hurry, need a help or solution. Could you please check it this issues and help me? Hope to hear from you soon, Thanks again. Arnob Mahmud Mobile Developer get it live GmbH R?merpfad 5 61130 Nidderau Germany t: +49 (0) 6187 - 476 - 0100 f: +49 (0) 6187 - 419 - 0697 arnob at get-it-live.com www.get-it-live.com Managing Director: Jan Husseini / Commercial register: local court Hanau, HRB 94959 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160421/1c625129/attachment.html From matzew at apache.org Sat Apr 23 06:51:23 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Sat, 23 Apr 2016 12:51:23 +0200 Subject: [aerogear-dev] Google Summer of Code: AeroGear WebPush and UnifiedPush Server integration Message-ID: Hi all, I am very happy to welcome Idel Pivnitsky this year as our Google Summer of Code student. Idel is an active community member since last years GSoC project, where he directly worked on our WebPush Server effort. This year Idel will work on WebPush and its integration into our UnifiedPush Server. Please join me in welcoming Idel to work on WebPush at AeroGear this summer! Greeting, Matthias Attached is the abstract --------------------------------------------------------------------------------------------------- AeroGear WebPush and UnifiedPush Server integration Abstract: The AeroGear UnifiedPush Server is a powerful and scalable server that allows sending push notifications to different (mobile) platforms. And now it?s time to extend it and add supporting for a new WebPush protocol, which will allow to send push notifications to the web browsers, such as Google Chrome and Mozilla Firefox. The project also supposes integration of AeroGear WebPush Server with UPS, which will allow to send push notifications to any device without requirement to use vendor?s push? messaging systems (Google Cloud Messaging, Mozilla Push Service). Expected results: - Add WebPush support for Google Chrome and Mozilla Firefox browsers into UPS. - Integrate AeroGear WebPush server with UnifiedPush Server. - Good test coverage for the new code (unit and integration testing). - Documentation for all new developments and changes. - Demo applications for showing the work of WebPush protocol in action with UPS: - pure WebPush demo: AeroGear UPS to WebPush Server, which delivers to a browser/device? - GCM/MPS push, triggered by UPS. On browser/device push message is received on WebPush APIs. Possible additional tasks which could be done: - Java client for AppServer (similar as a current client for User Agents). - Rewrite java clients with native Java 9 HTTP/2 API. - Port webpush?codec directly to Netty. It will simplify WebPush Server code base and attract other developers to improve the core of the protocol. --------------------------------------------------------------------------------------------------- -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160423/73d94921/attachment.html From daniel.bevenius at gmail.com Sat Apr 23 10:20:36 2016 From: daniel.bevenius at gmail.com (Daniel Bevenius) Date: Sat, 23 Apr 2016 16:20:36 +0200 Subject: [aerogear-dev] Google Summer of Code: AeroGear WebPush and UnifiedPush Server integration In-Reply-To: References: Message-ID: Great news, glad to hear that! On 23 April 2016 at 12:51, Matthias Wessendorf wrote: > Hi all, > > I am very happy to welcome Idel Pivnitsky this year as our Google Summer > of Code student. Idel is an active community member since last years GSoC > project, where he directly worked on our WebPush Server effort. > > This year Idel will work on WebPush and its integration into our > UnifiedPush Server. > > Please join me in welcoming Idel to work on WebPush at AeroGear this > summer! > > Greeting, > Matthias > > Attached is the abstract > > > --------------------------------------------------------------------------------------------------- > AeroGear WebPush and UnifiedPush Server integration > > > Abstract: > The AeroGear UnifiedPush Server is a powerful and scalable server that > allows sending push notifications to different (mobile) platforms. And now > it?s time to extend it and add supporting for a new WebPush protocol, which > will allow to send push notifications to the web browsers, such as Google > Chrome and Mozilla Firefox. The project also supposes integration of > AeroGear WebPush Server with UPS, which will allow to send push > notifications to any device without requirement to use vendor?s push? > messaging systems (Google Cloud Messaging, Mozilla Push Service). > > > Expected results: > - Add WebPush support for Google Chrome and Mozilla Firefox browsers into > UPS. > - Integrate AeroGear WebPush server with UnifiedPush Server. > - Good test coverage for the new code (unit and integration testing). > - Documentation for all new developments and changes. > - Demo applications for showing the work of WebPush protocol in action > with UPS: > - pure WebPush demo: AeroGear UPS to WebPush Server, which delivers to a > browser/device? > - GCM/MPS push, triggered by UPS. On browser/device push message is > received on WebPush APIs. > > Possible additional tasks which could be done: > - Java client for AppServer (similar as a current client for User Agents). > - Rewrite java clients with native Java 9 HTTP/2 API. > - Port webpush?codec directly to Netty. It will simplify WebPush Server > code base and attract other developers to improve the core of the protocol. > > --------------------------------------------------------------------------------------------------- > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160423/995d585a/attachment.html From edewit at redhat.com Mon Apr 25 09:04:15 2016 From: edewit at redhat.com (Erik Jan de Wit) Date: Mon, 25 Apr 2016 15:04:15 +0200 Subject: [aerogear-dev] Facing a problem during using AeroGear OTP Cordova plugin!! In-Reply-To: <000501d19b62$3fd578b0$bf806a10$@get-it-live.com> References: <000501d19b62$3fd578b0$bf806a10$@get-it-live.com> Message-ID: Hi, The OTP plugin depends on the phonegap barcode scanner, could you send attach what is in the log? You can see the log by running `adb logcat` from the command line On Thu, Apr 21, 2016 at 2:10 AM, Arnob Mahmud wrote: > Hello, > > > > Hi, I am new in using this kind of features, Well I am facing a problem > which I can?t solve, on testing purpose I have created a black ionic > angularjs framework based mobile application where I am using AeroGear OTP > Cordova plugin and when I click the OTP button for scan I got an alert > message saying ?Sorry, the Android camera encountered a problem. You may > need to restart the device.? And I found no good documentation about it so > far!! I am stuck on it totally now and I am in a hurry, need a help or > solution. Could you please check it this issues and help me? > > > > Hope to hear from you soon, Thanks again. > > > > > > > > Arnob Mahmud > Mobile Developer > > get it live GmbH > R?merpfad 5 > 61130 Nidderau > Germany > > t: +49 (0) 6187 - 476 - 0100 <+4961874760100> > f: +49 (0) 6187 - 419 - 0697 <+4961874190697> > arnob at get-it-live.com > www.get-it-live.com > > > > Managing Director: Jan Husseini / Commercial register: local court Hanau, > HRB 94959 > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160425/d8bc8a58/attachment-0001.html From idel.pivnitskiy at gmail.com Mon Apr 25 15:32:24 2016 From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy) Date: Mon, 25 Apr 2016 22:32:24 +0300 Subject: [aerogear-dev] Google Summer of Code: AeroGear WebPush and UnifiedPush Server integration In-Reply-To: References:

Message-ID: Thank you friends! Happy to continue to work with you! WebPush protocol holds out great hope for this year and it will be cool to integrate it with UPS! Best regards, Idel Pivnitskiy -- Twitter: @idelpivnitskiy GitHub: @idelpivnitskiy On Sat, Apr 23, 2016 at 5:20 PM, Daniel Bevenius wrote: > Great news, glad to hear that! > > On 23 April 2016 at 12:51, Matthias Wessendorf wrote: > >> Hi all, >> >> I am very happy to welcome Idel Pivnitsky this year as our Google Summer >> of Code student. Idel is an active community member since last years GSoC >> project, where he directly worked on our WebPush Server effort. >> >> This year Idel will work on WebPush and its integration into our >> UnifiedPush Server. >> >> Please join me in welcoming Idel to work on WebPush at AeroGear this >> summer! >> >> Greeting, >> Matthias >> >> Attached is the abstract >> >> >> --------------------------------------------------------------------------------------------------- >> AeroGear WebPush and UnifiedPush Server integration >> >> >> Abstract: >> The AeroGear UnifiedPush Server is a powerful and scalable server that >> allows sending push notifications to different (mobile) platforms. And now >> it?s time to extend it and add supporting for a new WebPush protocol, which >> will allow to send push notifications to the web browsers, such as Google >> Chrome and Mozilla Firefox. The project also supposes integration of >> AeroGear WebPush Server with UPS, which will allow to send push >> notifications to any device without requirement to use vendor?s push? >> messaging systems (Google Cloud Messaging, Mozilla Push Service). >> >> >> Expected results: >> - Add WebPush support for Google Chrome and Mozilla Firefox browsers into >> UPS. >> - Integrate AeroGear WebPush server with UnifiedPush Server. >> - Good test coverage for the new code (unit and integration testing). >> - Documentation for all new developments and changes. >> - Demo applications for showing the work of WebPush protocol in action >> with UPS: >> - pure WebPush demo: AeroGear UPS to WebPush Server, which delivers to >> a browser/device? >> - GCM/MPS push, triggered by UPS. On browser/device push message is >> received on WebPush APIs. >> >> Possible additional tasks which could be done: >> - Java client for AppServer (similar as a current client for User Agents). >> - Rewrite java clients with native Java 9 HTTP/2 API. >> - Port webpush?codec directly to Netty. It will simplify WebPush Server >> code base and attract other developers to improve the core of the protocol. >> >> --------------------------------------------------------------------------------------------------- >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160425/437d9f78/attachment.html From lholmqui at redhat.com Mon Apr 25 15:47:44 2016 From: lholmqui at redhat.com (Luke Holmquist) Date: Mon, 25 Apr 2016 15:47:44 -0400 Subject: [aerogear-dev] Google Summer of Code: AeroGear WebPush and UnifiedPush Server integration In-Reply-To: References:

Message-ID: YAY, nice to see this (and by extension, the Mobile Web) getting some love On Mon, Apr 25, 2016 at 3:32 PM, Idel Pivnitskiy wrote: > Thank you friends! > > Happy to continue to work with you! WebPush protocol holds out great hope > for this year and it will be cool to integrate it with UPS! > > Best regards, > Idel Pivnitskiy > -- > Twitter: @idelpivnitskiy > GitHub: @idelpivnitskiy > > On Sat, Apr 23, 2016 at 5:20 PM, Daniel Bevenius < > daniel.bevenius at gmail.com> wrote: > >> Great news, glad to hear that! >> >> On 23 April 2016 at 12:51, Matthias Wessendorf wrote: >> >>> Hi all, >>> >>> I am very happy to welcome Idel Pivnitsky this year as our Google Summer >>> of Code student. Idel is an active community member since last years GSoC >>> project, where he directly worked on our WebPush Server effort. >>> >>> This year Idel will work on WebPush and its integration into our >>> UnifiedPush Server. >>> >>> Please join me in welcoming Idel to work on WebPush at AeroGear this >>> summer! >>> >>> Greeting, >>> Matthias >>> >>> Attached is the abstract >>> >>> >>> --------------------------------------------------------------------------------------------------- >>> AeroGear WebPush and UnifiedPush Server integration >>> >>> >>> Abstract: >>> The AeroGear UnifiedPush Server is a powerful and scalable server that >>> allows sending push notifications to different (mobile) platforms. And now >>> it?s time to extend it and add supporting for a new WebPush protocol, which >>> will allow to send push notifications to the web browsers, such as Google >>> Chrome and Mozilla Firefox. The project also supposes integration of >>> AeroGear WebPush Server with UPS, which will allow to send push >>> notifications to any device without requirement to use vendor?s push? >>> messaging systems (Google Cloud Messaging, Mozilla Push Service). >>> >>> >>> Expected results: >>> - Add WebPush support for Google Chrome and Mozilla Firefox browsers >>> into UPS. >>> - Integrate AeroGear WebPush server with UnifiedPush Server. >>> - Good test coverage for the new code (unit and integration testing). >>> - Documentation for all new developments and changes. >>> - Demo applications for showing the work of WebPush protocol in action >>> with UPS: >>> - pure WebPush demo: AeroGear UPS to WebPush Server, which delivers to >>> a browser/device? >>> - GCM/MPS push, triggered by UPS. On browser/device push message is >>> received on WebPush APIs. >>> >>> Possible additional tasks which could be done: >>> - Java client for AppServer (similar as a current client for User >>> Agents). >>> - Rewrite java clients with native Java 9 HTTP/2 API. >>> - Port webpush?codec directly to Netty. It will simplify WebPush Server >>> code base and attract other developers to improve the core of the protocol. >>> >>> --------------------------------------------------------------------------------------------------- >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160425/73ce633c/attachment.html From supittma at redhat.com Mon Apr 25 16:24:04 2016 From: supittma at redhat.com (Summers Pittman) Date: Mon, 25 Apr 2016 16:24:04 -0400 Subject: [aerogear-dev] Google Service Gradle Plugin Message-ID: I am currently working on setting up support for consuming the google-services.json file for our AeroGear Android Push. I can parse the file to extract the push values from it at runtime if the file is in the assets folder; however, the Google services plugin expects this to be in the project flavor root and thus outside of the classpath. What do you guys think? Ideally we wouldn't be dependent on Google's plugin and would put this file in assets. However if you use Google's services above and beyond push then we will either a) need to duplicate the file or b) intelligently detect if the plugin was used to build the project and consume the file as appropriate. Thoughts? Summers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160425/ef7c90a5/attachment.html From matzew at apache.org Mon Apr 25 21:14:57 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 26 Apr 2016 03:14:57 +0200 Subject: [aerogear-dev] Google Service Gradle Plugin In-Reply-To: References: Message-ID: How is the regerence impl. (gcm-playground) solving this? On Monday, 25 April 2016, Summers Pittman wrote: > I am currently working on setting up support for consuming the > google-services.json file for our AeroGear Android Push. I can parse the > file to extract the push values from it at runtime if the file is in the > assets folder; however, the Google services plugin expects this to be in > the project flavor root and thus outside of the classpath. > > What do you guys think? Ideally we wouldn't be dependent on Google's > plugin and would put this file in assets. However if you use Google's > services above and beyond push then we will either a) need to duplicate the > file or b) intelligently detect if the plugin was used to build the project > and consume the file as appropriate. > > Thoughts? > > Summers > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160426/02a5e78b/attachment-0001.html From arnob_t78 at yahoo.com Mon Apr 25 21:36:33 2016 From: arnob_t78 at yahoo.com (arnob mahmud) Date: Tue, 26 Apr 2016 01:36:33 +0000 (UTC) Subject: [aerogear-dev] 'aerogear-dev' References: <1672546206.2192096.1461634593117.JavaMail.yahoo.ref@mail.yahoo.com> Message-ID: <1672546206.2192096.1461634593117.JavaMail.yahoo@mail.yahoo.com> Hello, ? Hi, I amnew in using this kind of features, Well I am facing a problem which I can?tsolve, on testing purpose I have created a black ionic angularjs framework?based mobile application where I am using AeroGear OTP Cordova plugin andwhen I click the OTP button for scan I got an alert message saying ?Sorry, theAndroid camera encountered a problem. You may need to restart the device.? AndI found no good documentation about it so far!! I am stuck on it totally nowand I am in a hurry, need a help or solution. Could you please check it thisissues and help me? ?Hope tohear from you soon, Thanks again. Regards, Arnob -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160426/8bdbfc94/attachment.html From arnob_t78 at yahoo.com Mon Apr 25 21:45:36 2016 From: arnob_t78 at yahoo.com (arnob_t78) Date: Mon, 25 Apr 2016 18:45:36 -0700 (MST) Subject: [aerogear-dev] Facing a problem during using AeroGear OTP Cordova plugin Message-ID: <1461635136494-12472.post@n5.nabble.com> Hello, Hi, I am new in using this kind of features, Well I am facing a problem which I can?t solve, on testing purpose I have created a black ionic angularjs framework based mobile application where I am using AeroGear OTP Cordova plugin and when I click the OTP button for scan I got an alert message saying ?Sorry, the Android camera encountered a problem. You may need to restart the device.? And I found no good documentation about it so far!! I am stuck on it totally now and I am in a hurry, need a help or solution. Could you please check it this issues and help me? Hope to hear from you soon, Thanks again. Regards, Arnob -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Facing-a-problem-during-using-AeroGear-OTP-Cordova-plugin-tp12472.html Sent from the aerogear-dev mailing list archive at Nabble.com. From matzew at apache.org Sat Apr 30 07:22:04 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Sat, 30 Apr 2016 13:22:04 +0200 Subject: [aerogear-dev] Google Service Gradle Plugin In-Reply-To: References:

Message-ID: Or, we skip the plugin, and continue to rely on the sender_id / project_number, like now ? I think I am a bit sceptical if this plugin makes us go a route we perhaps don't want ? On Tue, Apr 26, 2016 at 3:14 AM, Matthias Wessendorf wrote: > How is the regerence impl. (gcm-playground) solving this? > > > On Monday, 25 April 2016, Summers Pittman wrote: > >> I am currently working on setting up support for consuming the >> google-services.json file for our AeroGear Android Push. I can parse the >> file to extract the push values from it at runtime if the file is in the >> assets folder; however, the Google services plugin expects this to be in >> the project flavor root and thus outside of the classpath. >> >> What do you guys think? Ideally we wouldn't be dependent on Google's >> plugin and would put this file in assets. However if you use Google's >> services above and beyond push then we will either a) need to duplicate the >> file or b) intelligently detect if the plugin was used to build the project >> and consume the file as appropriate. >> >> Thoughts? >> >> Summers >> > > > -- > Sent from Gmail Mobile > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160430/7acbc7d3/attachment.html From supittma at redhat.com Sat Apr 30 14:09:57 2016 From: supittma at redhat.com (Summers Pittman) Date: Sat, 30 Apr 2016 14:09:57 -0400 Subject: [aerogear-dev] Google Service Gradle Plugin In-Reply-To: References:

Message-ID: I'm fine with this. We might want to think about offering our own build plugin in a future release On Apr 30, 2016 7:23 AM, "Matthias Wessendorf" wrote: > Or, we skip the plugin, and continue to rely on the sender_id / > project_number, like now ? > > I think I am a bit sceptical if this plugin makes us go a route we perhaps > don't want ? > > On Tue, Apr 26, 2016 at 3:14 AM, Matthias Wessendorf > wrote: > >> How is the regerence impl. (gcm-playground) solving this? >> >> >> On Monday, 25 April 2016, Summers Pittman wrote: >> >>> I am currently working on setting up support for consuming the >>> google-services.json file for our AeroGear Android Push. I can parse the >>> file to extract the push values from it at runtime if the file is in the >>> assets folder; however, the Google services plugin expects this to be in >>> the project flavor root and thus outside of the classpath. >>> >>> What do you guys think? Ideally we wouldn't be dependent on Google's >>> plugin and would put this file in assets. However if you use Google's >>> services above and beyond push then we will either a) need to duplicate the >>> file or b) intelligently detect if the plugin was used to build the project >>> and consume the file as appropriate. >>> >>> Thoughts? >>> >>> Summers >>> >> >> >> -- >> Sent from Gmail Mobile >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160430/8482a1c4/attachment.html