From corinnekrych at gmail.com  Tue Mar  1 10:15:14 2016
From: corinnekrych at gmail.com (Corinne Krych)
Date: Tue, 1 Mar 2016 16:15:14 +0100
Subject: [aerogear-dev] New aerogear-ios-http and aerogear-ios-oauth2
	releases are ready to test
Message-ID: <CAL8vO=eHzEV8+QuvgXgsP3be=Ww_BAWVp5HCsz2JEOAYVNn16w@mail.gmail.com>

Hello iOS AeroGear Lovers,

A new release 0.5.0 is under preparation for AeroGearHttp and
AeroGearOAuth2, this new release brings:
- simplification of the API for doing request. See README usage update [1]
- more flexibility to define your own validate and response by making then
closure. See more in unit tests [2].

As always branches are available for you to test [3], let us know if you
find any issues with our upcoming 0.5.0 libraries.
If everything goes well, pods will be released on Friday.

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-http#example-usage
[2]
https://github.com/aerogear/aerogear-ios-http/blob/master/AeroGearHttpTests/JSONResponseSerializerTests.swift#L64
https://github.com/aerogear/aerogear-ios-http/blob/master/AeroGearHttpTests/JSONResponseSerializerTests.swift#L154
[3] https://github.com/aerogear/aerogear-ios-http/tree/release.0.5.0
https://github.com/aerogear/aerogear-ios-oauth2/tree/uses.release.0.5.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160301/13c7637e/attachment.html 

From matzew at apache.org  Wed Mar  2 06:00:34 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 2 Mar 2016 12:00:34 +0100
Subject: [aerogear-dev] Staging of UnifiedPush Server 1.1.1
In-Reply-To: <CAD_dpu00bkAVTcAssbXu4Qg_dTOhvjVnV3RHNNnS7kDYaETfTg@mail.gmail.com>
References: <CAD_dpu1dVQeEAmDL6Mp1QnvGfCaD-EFZxObotxVLmQ=DOb3vuQ@mail.gmail.com>
	<CAAnALHns0YKee+zm25V+0qDn7-KQ-YFZzHmio+Cdc06q6cqcNA@mail.gmail.com>
	<CAAnALHkB6cF8RWiRB-=jrGQQb=tSGY80dWczJMxJrwHnjYYf5w@mail.gmail.com>
	<CAD_dpu2D3PRJU2sTXp8qDRDR1p-sgp6PgazCPjKfqsK-51wHcw@mail.gmail.com>
	<CAD_dpu00bkAVTcAssbXu4Qg_dTOhvjVnV3RHNNnS7kDYaETfTg@mail.gmail.com>
Message-ID: <CAAg5f2SUx4e=gBvb05wgaQ88VOUwGEr3qD6LWNqQC+_mT+iMMA@mail.gmail.com>

A month later, wondering... what's the state here ?



On Tue, Feb 2, 2016 at 11:08 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Ok,
> So we dropped the previous staging repo and a new one has just been
> created containing an important fix :
>
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7630/
>
> Please test this release.
>
> Sebi
>
>
> On Mon, Feb 1, 2016 at 9:13 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> Yes, these issues are not really "minor" IMO so we should fix them.
>>
>> On Fri, Jan 29, 2016 at 4:10 PM, Lukas Fryc <lfryc at redhat.com> wrote:
>>
>>> I have deployed the release to my OpenShift sandbox:
>>> https://upsrelease111-aerogearz.rhcloud.com/ag-push/
>>> (if someone else want to test it, feel free to use it, just create your
>>> own push app)
>>>
>>>
>>> I've also tested Android variant in Cordova app and pushing via REST
>>> API. Generally it works, however...
>>>
>>> I've noticed several minor issues:
>>>
>>>    - AGPUSH-1570 <https://issues.jboss.org/browse/AGPUSH-1570> False
>>>    Error notification in App Creation wizard
>>>    - AGPUSH-1571 <https://issues.jboss.org/browse/AGPUSH-1571>UPS
>>>    console initially starts without Welcome page / Blank Slate
>>>    - AGPUSH-1572 <https://issues.jboss.org/browse/AGPUSH-1572> UPS
>>>    again shows invalid Pending state for Push Message that was delivered
>>>
>>>
>>> I believe we should fix those and restage next week. WDYT?
>>>
>>>
>>> If someone could test also other platforms of own choice, please do so!
>>> You can use my deployment ^^^
>>>
>>>
>>> Cheers,
>>>
>>> ~ Lukas
>>>
>>> On Wed, Jan 27, 2016 at 5:31 PM, Lukas Fryc <lfryc at redhat.com> wrote:
>>>
>>>> Thanks Sebi!
>>>>
>>>> I will give it a try.
>>>>
>>>> On Wed, Jan 27, 2016 at 3:44 PM, Sebastien Blanc <scm.blanc at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Folk,
>>>>>
>>>>> I'm happy to announce that UPS 1.1.1 has been staged  :
>>>>>
>>>>>
>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7587
>>>>>
>>>>> Release notes can be found here :
>>>>>
>>>>>
>>>>> https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12313724&version=12327457&_sscc=t
>>>>>
>>>>> Please give it a try, I plan to hit the magic button Friday end of the
>>>>> day.
>>>>>
>>>>> Sebi
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Luk?? Fry?
>>>> Software Engineer
>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>
>>>
>>>
>>>
>>> --
>>> Luk?? Fry?
>>> Software Engineer
>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>
>>> _______________________________________________
>>> 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/20160302/7d32fb47/attachment.html 

From lholmqui at redhat.com  Wed Mar  2 09:14:31 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Wed, 2 Mar 2016 09:14:31 -0500
Subject: [aerogear-dev] quick question - Safari Push notifications
In-Reply-To: <767F4862-1AAF-4849-B4D2-E19C91007EEE@wots.mobi>
References: <767F4862-1AAF-4849-B4D2-E19C91007EEE@wots.mobi>
Message-ID: <CALD3Fd0-WxuZpbz75s_Y0GWK7zB3j8VH1uiFpLMnu47GeXab3Q@mail.gmail.com>

On Tue, Mar 1, 2016 at 4:27 PM, Darren Coles <darrenc at wots.mobi> wrote:

> Hi
>
> As I?ve seen your the one doing all the Safari Push notifications, I just
> wanted to ask if that?s in the latest release? 1.1.0 UPS
>

> I have everything setup, followed your blog to the letter and a few others.
>
> On the webpage via safari I get the popup for notifications and it
> registers it on the Aerogear UPS when I accept.
>
> In the UPS admin I can see the safari token.
>
> However when I send a message it always says successful, but nothing ever
> appears on the my system for notifications.
>
> I?m using the .P12 web.com.rhcloud.push-wots certificate with password,
> which is a web push certificate fro Apple.
> The backend shows successful even when I just send to the safari variant.
>
in the UPS, are you selecting the "production" option when uploading the
Cert?

>
> (Will Safari work with normal IOS push certificate, trying that today as
> going around in circles at the moment.
>
> Can Aerogear actually handle Safari notifications and do you have a bit
> more of a HOWTO.
>
> The work on this platform is fantastic, and everything else works like a
> dream with all the mobile devices and chrome browsers.
> This is just the last thing that is driving me mad. And I can?t find any
> logs to tell me that anything is going wrong.
>
> If you could take a couple of minutes to point me in the right direction I
> would be so grateful.
>

I'm glad you like the platform.  i haven't done any Safari work in probably
a year now,  so things might have changed a little bit from when i wrote
that blog post, but if i get the chance, i'll try to go through it again.



>
> Thank you in advance, have a great day.
>
>
> Darren Coles
>
> mobile: 0420 908 356
> email: darrenc at wots.mobi
> web: http://www.wots.mobi
>
>
> The information in this e-mail is confidential and intended solely for
> the use of the individual to whom it was addressed. If you are not the
> intended recipient, please be advised that if you have received this e-mail
> in error then any use, dissemination, forwarding, printing or copying of
> this e-mail is strictly prohibited. If you have received this e-mail in
> error, please inform the sender by using the reply facility in your
> e-mail software and then delete from your system. Although Word On The
> Street, takes precautions to minimise the risk of transmitting computer
> viruses, it is your responsibility to carry out your own virus checks on
> this e-mail and any attachments. Please note that neither Word On The
> Street nor the sender accepts any responsibility for viruses.  Internet
> communications are not secure and therefore Word On The Street. does not
> accept legal responsibility for the contents of this e-mail. Any views
> or opinions presented are solely those of the author and do not
> necessarily represent those Word On The Street.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160302/117590e6/attachment-0001.html 

From lholmqui at redhat.com  Wed Mar  2 09:17:54 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Wed, 2 Mar 2016 09:17:54 -0500
Subject: [aerogear-dev] quick question - Safari Push notifications
In-Reply-To: <CALD3Fd0-WxuZpbz75s_Y0GWK7zB3j8VH1uiFpLMnu47GeXab3Q@mail.gmail.com>
References: <767F4862-1AAF-4849-B4D2-E19C91007EEE@wots.mobi>
	<CALD3Fd0-WxuZpbz75s_Y0GWK7zB3j8VH1uiFpLMnu47GeXab3Q@mail.gmail.com>
Message-ID: <CALD3Fd1bm7FdS4yMd4afiRtg8SOmCC4H5Vkk+Yn1CYtZmodctg@mail.gmail.com>

So i just quickly re-read my blog post on this.

You should be able to do Safari notifications out of the box on the latest
UPS,  just by using the iOS variant.  You would just use the Web
Certificate and choose the production options.( this is how it used to be,
 i think ).

On Wed, Mar 2, 2016 at 9:14 AM, Luke Holmquist <lholmqui at redhat.com> wrote:

>
>
> On Tue, Mar 1, 2016 at 4:27 PM, Darren Coles <darrenc at wots.mobi> wrote:
>
>> Hi
>>
>> As I?ve seen your the one doing all the Safari Push notifications, I just
>> wanted to ask if that?s in the latest release? 1.1.0 UPS
>>
>
>> I have everything setup, followed your blog to the letter and a few
>> others.
>>
>> On the webpage via safari I get the popup for notifications and it
>> registers it on the Aerogear UPS when I accept.
>>
>> In the UPS admin I can see the safari token.
>>
>> However when I send a message it always says successful, but nothing ever
>> appears on the my system for notifications.
>>
>> I?m using the .P12 web.com.rhcloud.push-wots certificate with password,
>> which is a web push certificate fro Apple.
>> The backend shows successful even when I just send to the safari variant.
>>
> in the UPS, are you selecting the "production" option when uploading the
> Cert?
>
>>
>> (Will Safari work with normal IOS push certificate, trying that today as
>> going around in circles at the moment.
>>
>> Can Aerogear actually handle Safari notifications and do you have a bit
>> more of a HOWTO.
>>
>> The work on this platform is fantastic, and everything else works like a
>> dream with all the mobile devices and chrome browsers.
>> This is just the last thing that is driving me mad. And I can?t find any
>> logs to tell me that anything is going wrong.
>>
>> If you could take a couple of minutes to point me in the right direction
>> I would be so grateful.
>>
>
> I'm glad you like the platform.  i haven't done any Safari work in
> probably a year now,  so things might have changed a little bit from when i
> wrote that blog post, but if i get the chance, i'll try to go through it
> again.
>
>
>
>>
>> Thank you in advance, have a great day.
>>
>>
>> Darren Coles
>>
>> mobile: 0420 908 356
>> email: darrenc at wots.mobi
>> web: http://www.wots.mobi
>>
>>
>> The information in this e-mail is confidential and intended solely for
>> the use of the individual to whom it was addressed. If you are not the
>> intended recipient, please be advised that if you have received this e-mail
>> in error then any use, dissemination, forwarding, printing or copying of
>> this e-mail is strictly prohibited. If you have received this e-mail in
>> error, please inform the sender by using the reply facility in your
>> e-mail software and then delete from your system. Although Word On The
>> Street, takes precautions to minimise the risk of transmitting computer
>> viruses, it is your responsibility to carry out your own virus checks on
>> this e-mail and any attachments. Please note that neither Word On The
>> Street nor the sender accepts any responsibility for viruses.  Internet
>> communications are not secure and therefore Word On The Street. does not
>> accept legal responsibility for the contents of this e-mail. Any views
>> or opinions presented are solely those of the author and do not
>> necessarily represent those Word On The Street.
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160302/8254ec40/attachment.html 

From matzew at apache.org  Thu Mar  3 12:55:30 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 3 Mar 2016 18:55:30 +0100
Subject: [aerogear-dev] Staging of UnifiedPush Server 1.1.1
In-Reply-To: <CAAg5f2SUx4e=gBvb05wgaQ88VOUwGEr3qD6LWNqQC+_mT+iMMA@mail.gmail.com>
References: <CAD_dpu1dVQeEAmDL6Mp1QnvGfCaD-EFZxObotxVLmQ=DOb3vuQ@mail.gmail.com>
	<CAAnALHns0YKee+zm25V+0qDn7-KQ-YFZzHmio+Cdc06q6cqcNA@mail.gmail.com>
	<CAAnALHkB6cF8RWiRB-=jrGQQb=tSGY80dWczJMxJrwHnjYYf5w@mail.gmail.com>
	<CAD_dpu2D3PRJU2sTXp8qDRDR1p-sgp6PgazCPjKfqsK-51wHcw@mail.gmail.com>
	<CAD_dpu00bkAVTcAssbXu4Qg_dTOhvjVnV3RHNNnS7kDYaETfTg@mail.gmail.com>
	<CAAg5f2SUx4e=gBvb05wgaQ88VOUwGEr3qD6LWNqQC+_mT+iMMA@mail.gmail.com>
Message-ID: <CAAg5f2RvHNDfBE7EmCE=Nie1Q9Det49MagK1rLZUsuqZ9_uNjg@mail.gmail.com>

here is the new URL:


https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7809/



let me know - Monday I will release....

On Wed, Mar 2, 2016 at 12:00 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> A month later, wondering... what's the state here ?
>
>
>
> On Tue, Feb 2, 2016 at 11:08 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> Ok,
>> So we dropped the previous staging repo and a new one has just been
>> created containing an important fix :
>>
>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7630/
>>
>> Please test this release.
>>
>> Sebi
>>
>>
>> On Mon, Feb 1, 2016 at 9:13 AM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>> Yes, these issues are not really "minor" IMO so we should fix them.
>>>
>>> On Fri, Jan 29, 2016 at 4:10 PM, Lukas Fryc <lfryc at redhat.com> wrote:
>>>
>>>> I have deployed the release to my OpenShift sandbox:
>>>> https://upsrelease111-aerogearz.rhcloud.com/ag-push/
>>>> (if someone else want to test it, feel free to use it, just create your
>>>> own push app)
>>>>
>>>>
>>>> I've also tested Android variant in Cordova app and pushing via REST
>>>> API. Generally it works, however...
>>>>
>>>> I've noticed several minor issues:
>>>>
>>>>    - AGPUSH-1570 <https://issues.jboss.org/browse/AGPUSH-1570> False
>>>>    Error notification in App Creation wizard
>>>>    - AGPUSH-1571 <https://issues.jboss.org/browse/AGPUSH-1571>UPS
>>>>    console initially starts without Welcome page / Blank Slate
>>>>    - AGPUSH-1572 <https://issues.jboss.org/browse/AGPUSH-1572> UPS
>>>>    again shows invalid Pending state for Push Message that was delivered
>>>>
>>>>
>>>> I believe we should fix those and restage next week. WDYT?
>>>>
>>>>
>>>> If someone could test also other platforms of own choice, please do so!
>>>> You can use my deployment ^^^
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> ~ Lukas
>>>>
>>>> On Wed, Jan 27, 2016 at 5:31 PM, Lukas Fryc <lfryc at redhat.com> wrote:
>>>>
>>>>> Thanks Sebi!
>>>>>
>>>>> I will give it a try.
>>>>>
>>>>> On Wed, Jan 27, 2016 at 3:44 PM, Sebastien Blanc <scm.blanc at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Folk,
>>>>>>
>>>>>> I'm happy to announce that UPS 1.1.1 has been staged  :
>>>>>>
>>>>>>
>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7587
>>>>>>
>>>>>> Release notes can be found here :
>>>>>>
>>>>>>
>>>>>> https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12313724&version=12327457&_sscc=t
>>>>>>
>>>>>> Please give it a try, I plan to hit the magic button Friday end of
>>>>>> the day.
>>>>>>
>>>>>> Sebi
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Luk?? Fry?
>>>>> Software Engineer
>>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Luk?? Fry?
>>>> Software Engineer
>>>> Red Hat Mobile | AeroGear.org, FeedHenry.org
>>>>
>>>> _______________________________________________
>>>> 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/20160303/fc98e2b9/attachment.html 

From matzew at apache.org  Fri Mar  4 02:58:22 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 4 Mar 2016 08:58:22 +0100
Subject: [aerogear-dev] Java MPNS release (0.3.0)
Message-ID: <CAAg5f2QWm=51ULs=kFwB+eDd-aafvuanj5i0z8HihoVpzgHPrA@mail.gmail.com>

Hi,

from the community, we got a PR and the request to ship a new version:
https://github.com/aerogear/java-mpns/pull/11

Besides that, we were also updating the parent pom.

The staging repo is located here:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7817/org/jboss/aerogear/windows/java-mpns/0.3.0/

Let me know if there are any concerns, otherwise I will release the JAR to
Maven central on Monday morning

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/20160304/99ae2906/attachment-0001.html 

From corinnekrych at gmail.com  Fri Mar  4 03:01:24 2016
From: corinnekrych at gmail.com (Corinne Krych)
Date: Fri, 4 Mar 2016 09:01:24 +0100
Subject: [aerogear-dev] New aerogear-ios-http and aerogear-ios-oauth2
 releases are ready to test
In-Reply-To: <CAL8vO=eHzEV8+QuvgXgsP3be=Ww_BAWVp5HCsz2JEOAYVNn16w@mail.gmail.com>
References: <CAL8vO=eHzEV8+QuvgXgsP3be=Ww_BAWVp5HCsz2JEOAYVNn16w@mail.gmail.com>
Message-ID: <CAL8vO=dgFyzY5Bg4Ldf1Ujg=jX6KKPOvN4ff=mt-qimxigQuOg@mail.gmail.com>

Hello

The libs have been released and are available on CocoaPods:
https://github.com/CocoaPods/Specs/blob/master/Specs/AeroGearHttp/0.5.1/AeroGearHttp.podspec.json
https://github.com/CocoaPods/Specs/blob/master/Specs/AeroGearOAuth2/0.5.1/AeroGearOAuth2.podspec.json

++
Corinne.


On 1 March 2016 at 16:15, Corinne Krych <corinnekrych at gmail.com> wrote:

> Hello iOS AeroGear Lovers,
>
> A new release 0.5.0 is under preparation for AeroGearHttp and
> AeroGearOAuth2, this new release brings:
> - simplification of the API for doing request. See README usage update [1]
> - more flexibility to define your own validate and response by making then
> closure. See more in unit tests [2].
>
> As always branches are available for you to test [3], let us know if you
> find any issues with our upcoming 0.5.0 libraries.
> If everything goes well, pods will be released on Friday.
>
> ++
> Corinne
> [1] https://github.com/aerogear/aerogear-ios-http#example-usage
> [2]
> https://github.com/aerogear/aerogear-ios-http/blob/master/AeroGearHttpTests/JSONResponseSerializerTests.swift#L64
>
> https://github.com/aerogear/aerogear-ios-http/blob/master/AeroGearHttpTests/JSONResponseSerializerTests.swift#L154
> [3] https://github.com/aerogear/aerogear-ios-http/tree/release.0.5.0
> https://github.com/aerogear/aerogear-ios-oauth2/tree/uses.release.0.5.0
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160304/c90ba3c3/attachment.html 

From matzew at apache.org  Fri Mar  4 06:16:51 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 4 Mar 2016 12:16:51 +0100
Subject: [aerogear-dev] Google Summer of Code 2016
In-Reply-To: <CAPy+R7binq5QS+tvammpiR_zSZevpGeJkmV50+5u0hdmmkkM8A@mail.gmail.com>
References: <CAAg5f2Tg6JOb0Q-QbNOkKnZnaDMt-w_UCTBEH6X=+O6cKZOOoA@mail.gmail.com>
	<CAAg5f2QF4L6QqxMSXcEpg13VqWVevUven3JoG_4qVgH3zyuqzw@mail.gmail.com>
	<CAL8vO=fTj+WUYiYAtS5z9n4FNyoNZBUyiDXvn=z_h4gadvRY9w@mail.gmail.com>
	<CAAg5f2Q0DbZ_PvQMwpiKAOXsKQd_6knCMYXkABwhvX7rkWfNmw@mail.gmail.com>
	<CAPy+R7ZLB0ULFaYY-d7MiXPgu91gsKXUbwpomkN0DTzcfMhD=A@mail.gmail.com>
	<56B845D0-7ACC-4EF3-AB5D-8228F68B2B1B@redhat.com>
	<CAL8vO=fs5xDoL2AYMj9sTGYeKfs=2BQLFW2fYqGf+1XjB8JJqQ@mail.gmail.com>
	<CAAg5f2QZFwoMszRD7AvQ6pv5mXPsZJ4izBZtiLkMxoDmv5C0kQ@mail.gmail.com>
	<CAPy+R7binq5QS+tvammpiR_zSZevpGeJkmV50+5u0hdmmkkM8A@mail.gmail.com>
Message-ID: <CAAg5f2RnCGU2pYULwq=BCH5hH7J0HZSJGo2SOnuCgFwxKOByVg@mail.gmail.com>

Added the UPS demo to the list:
https://developer.jboss.org/wiki/JBossCommunityGoogleSummerOfCode2016Ideas#jive_content_id_Push_Notification_demo_case_for_Unified_Push_Server

On Thu, Feb 25, 2016 at 5:54 PM, Jay Balunas <jbalunas at redhat.com> wrote:

> I think using AeroGear dev is appropriate for this, but we should also
> make sure the linked doc from Heiko is updates.
>
> Perhaps a link in those entries to this mailing list would be a good idea?
>
> On Thu, Feb 25, 2016 at 9:36 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Corinne, can you route them to here?
>> The idea of open source is not just developing code, also to understand
>> the more important community aspect of it.
>> I haven't seen any notice of a student here for that particular project.
>> Right now, I'd never give a positive vote, as community > code
>>
>> -M
>>
>> On Thu, Feb 25, 2016 at 3:22 PM, Corinne Krych <corinnekrych at gmail.com>
>> wrote:
>>
>>> @Heiko I've done it already and students are already reaching me ;)
>>>
>>> On 25 February 2016 at 14:40, Heiko W.Rupp <hrupp at redhat.com> wrote:
>>>
>>>> On 25 Feb 2016, at 14:24, Jay Balunas wrote:
>>>>
>>>> > Both a really good suggestions, and would be very interested if they
>>>> > worked
>>>> > out!
>>>>
>>>> Put them on
>>>>
>>>> https://developer.jboss.org/wiki/JBossCommunityGoogleSummerOfCode2016Ideas
>>>> Tuesday we will know if JBoss has been accepted and then Students will
>>>> flood us :)
>>>> _______________________________________________
>>>> 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
>>
>> _______________________________________________
>> 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/20160304/1a053a98/attachment.html 

From devanshu911 at gmail.com  Mon Mar  7 02:14:20 2016
From: devanshu911 at gmail.com (Devanshu Singh)
Date: Mon, 7 Mar 2016 12:44:20 +0530
Subject: [aerogear-dev]  Google Summer of Code 2016
Message-ID: <CAE8ah42dbMQDUsTyFn_UeNABD8LML19y2n53wY9aHk=ZXibiRQ@mail.gmail.com>

Hello AeroGear Developers,

I am a student based in India with keen interest in Java and related
technologies.I also have been working on mobile platforms lately.Browsing
the GSoC ideas list on JBoss website, I find ?Push Notification demo case
for Unified Push Server? particularly engaging.I have previous experience
in working with Java EE and Mobile platforms like Wildfly Swarm, Keycloak
and Android.I also have intentions to use the UPS for my own mobile
projects in the future.
Thus I would love to contribute to this project for GSoC 2016.

I have been contributing to the JBoss Community for a long time,
particularly to the JBoss Forge project.I have also previously successfully
completed a GSoC project for Forge under George Gastaldi last year.

I have been through the AeroGear cookbooks and guides.

I will be looking forward to a great collaboration with the AeroGear
community in improving and adding new features to Aerodoc.

Best Regards,
Devanshu Singh.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160307/f9afc42a/attachment.html 

From matzew at apache.org  Tue Mar  8 04:00:40 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 8 Mar 2016 10:00:40 +0100
Subject: [aerogear-dev] UPS 1.1.1.Final
Message-ID: <CAAg5f2RJXMNeL9-UrQJUfcmXw9C5ix+sw1i0Q=GeQow5Q10QGA@mail.gmail.com>

Hi,

the UPS 1.1.1.Final is now availabe!
https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.1.1.Final

Have fun!

-- 
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/20160308/35d0cdc3/attachment.html 

From matzew at apache.org  Wed Mar  9 04:37:33 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 9 Mar 2016 10:37:33 +0100
Subject: [aerogear-dev] Google Summer of Code 2016
In-Reply-To: <CAE8ah42dbMQDUsTyFn_UeNABD8LML19y2n53wY9aHk=ZXibiRQ@mail.gmail.com>
References: <CAE8ah42dbMQDUsTyFn_UeNABD8LML19y2n53wY9aHk=ZXibiRQ@mail.gmail.com>
Message-ID: <CAAg5f2R+4W5y-mcbaZon4E7z8sbfScS3ZWt8dFfx3GtDiKZUZw@mail.gmail.com>

Hi Devanshu,

thanks for reaching out and showing interest in the project. I think a good
start is getting familiar with the AeroDoc demo and the UPS itself. Also,
we don't mind PRs :) e.g. if you find something in AGPUSH JIRA that sounds
cool, you are welcome to already contribute to it, as a getting started
with our community and its code



On Mon, Mar 7, 2016 at 8:14 AM, Devanshu Singh <devanshu911 at gmail.com>
wrote:

> Hello AeroGear Developers,
>
> I am a student based in India with keen interest in Java and related
> technologies.I also have been working on mobile platforms lately.Browsing
> the GSoC ideas list on JBoss website, I find ?Push Notification demo case
> for Unified Push Server? particularly engaging.I have previous experience
> in working with Java EE and Mobile platforms like Wildfly Swarm, Keycloak
> and Android.I also have intentions to use the UPS for my own mobile
> projects in the future.
> Thus I would love to contribute to this project for GSoC 2016.
>
> I have been contributing to the JBoss Community for a long time,
> particularly to the JBoss Forge project.I have also previously successfully
> completed a GSoC project for Forge under George Gastaldi last year.
>
> I have been through the AeroGear cookbooks and guides.
>
> I will be looking forward to a great collaboration with the AeroGear
> community in improving and adding new features to Aerodoc.
>
> Best Regards,
> Devanshu Singh.
>
> _______________________________________________
> 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/20160309/a4f49836/attachment-0001.html 

From vivek.pandey at pinelabs.com  Thu Mar 10 05:03:07 2016
From: vivek.pandey at pinelabs.com (Vivek Pandey)
Date: Thu, 10 Mar 2016 15:33:07 +0530
Subject: [aerogear-dev] UPS 1.1.1.Final
In-Reply-To: <CAAg5f2RJXMNeL9-UrQJUfcmXw9C5ix+sw1i0Q=GeQow5Q10QGA@mail.gmail.com>
References: <CAAg5f2RJXMNeL9-UrQJUfcmXw9C5ix+sw1i0Q=GeQow5Q10QGA@mail.gmail.com>
Message-ID: <006d01d17ab4$0bb92500$232b6f00$@pinelabs.com>

Great news!!

 

I can confirm that the bug I logged https://issues.jboss.org/browse/AGPUSH-1568 is fixed.

However, on upgradation I ran into another problem https://issues.jboss.org/browse/AGPUSH-1594

 

Thanks,

Vivek

 

From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf
Sent: Tuesday, March 08, 2016 2:31 PM
To: AeroGear Developer Mailing List; aerogear-users at lists.jboss.org
Subject: [aerogear-dev] UPS 1.1.1.Final

 

Hi,

 

the UPS 1.1.1.Final is now availabe!

https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.1.1.Final

 

Have fun!

 

-- 

Matthias Wessendorf 

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf


This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160310/ffd4fe1b/attachment.html 

From matzew at apache.org  Thu Mar 10 05:40:31 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 10 Mar 2016 11:40:31 +0100
Subject: [aerogear-dev] UPS 1.1.1.Final
In-Reply-To: <006d01d17ab4$0bb92500$232b6f00$@pinelabs.com>
References: <CAAg5f2RJXMNeL9-UrQJUfcmXw9C5ix+sw1i0Q=GeQow5Q10QGA@mail.gmail.com>
	<006d01d17ab4$0bb92500$232b6f00$@pinelabs.com>
Message-ID: <CAAg5f2TbiOv66HZAKvn_dnsvs62zTHR8DYHjdP=DWmG6ceo2Pw@mail.gmail.com>

can you add a few more details? how to reproduce this ?

I will take a look

On Thu, Mar 10, 2016 at 11:03 AM, Vivek Pandey <vivek.pandey at pinelabs.com>
wrote:

> Great news!!
>
>
>
> I can confirm that the bug I logged
> https://issues.jboss.org/browse/AGPUSH-1568 is fixed.
>
> However, on upgradation I ran into another problem
> https://issues.jboss.org/browse/AGPUSH-1594
>
>
>
> Thanks,
>
> Vivek
>
>
>
> *From:* aerogear-dev-bounces at lists.jboss.org [mailto:
> aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf
> *Sent:* Tuesday, March 08, 2016 2:31 PM
> *To:* AeroGear Developer Mailing List; aerogear-users at lists.jboss.org
> *Subject:* [aerogear-dev] UPS 1.1.1.Final
>
>
>
> Hi,
>
>
>
> the UPS 1.1.1.Final is now availabe!
>
>
> https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.1.1.Final
>
>
>
> Have fun!
>
>
>
> --
>
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> ------------------------------
> This message may contain privileged and confidential information and is
> solely for the use of intended recipient. The views expressed in this email
> are those of the sender and not of Pine Labs. The recipient should check
> this email and attachments for the presence of viruses / malwares etc. Pine
> Labs accepts no liability for any damage caused by any virus transmitted by
> this email. Pine Labs may monitor and record all emails.
> ------------------------------
>
>
> _______________________________________________
> 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/20160310/523ae17b/attachment.html 

From matzew at apache.org  Thu Mar 10 05:48:08 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 10 Mar 2016 11:48:08 +0100
Subject: [aerogear-dev] UPS 1.1.1.Final
In-Reply-To: <CAAg5f2TbiOv66HZAKvn_dnsvs62zTHR8DYHjdP=DWmG6ceo2Pw@mail.gmail.com>
References: <CAAg5f2RJXMNeL9-UrQJUfcmXw9C5ix+sw1i0Q=GeQow5Q10QGA@mail.gmail.com>
	<006d01d17ab4$0bb92500$232b6f00$@pinelabs.com>
	<CAAg5f2TbiOv66HZAKvn_dnsvs62zTHR8DYHjdP=DWmG6ceo2Pw@mail.gmail.com>
Message-ID: <CAAg5f2QceJEkBS78-dVRUBhR5TC0aJwGhd9hQ46hcTj=CqruUQ@mail.gmail.com>

Looks like null is passed on the categories, for updating, the device
metadata.

On it

On Thu, Mar 10, 2016 at 11:40 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> can you add a few more details? how to reproduce this ?
>
> I will take a look
>
> On Thu, Mar 10, 2016 at 11:03 AM, Vivek Pandey <vivek.pandey at pinelabs.com>
> wrote:
>
>> Great news!!
>>
>>
>>
>> I can confirm that the bug I logged
>> https://issues.jboss.org/browse/AGPUSH-1568 is fixed.
>>
>> However, on upgradation I ran into another problem
>> https://issues.jboss.org/browse/AGPUSH-1594
>>
>>
>>
>> Thanks,
>>
>> Vivek
>>
>>
>>
>> *From:* aerogear-dev-bounces at lists.jboss.org [mailto:
>> aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf
>> *Sent:* Tuesday, March 08, 2016 2:31 PM
>> *To:* AeroGear Developer Mailing List; aerogear-users at lists.jboss.org
>> *Subject:* [aerogear-dev] UPS 1.1.1.Final
>>
>>
>>
>> Hi,
>>
>>
>>
>> the UPS 1.1.1.Final is now availabe!
>>
>>
>> https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.1.1.Final
>>
>>
>>
>> Have fun!
>>
>>
>>
>> --
>>
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> ------------------------------
>> This message may contain privileged and confidential information and is
>> solely for the use of intended recipient. The views expressed in this email
>> are those of the sender and not of Pine Labs. The recipient should check
>> this email and attachments for the presence of viruses / malwares etc. Pine
>> Labs accepts no liability for any damage caused by any virus transmitted by
>> this email. Pine Labs may monitor and record all emails.
>> ------------------------------
>>
>>
>> _______________________________________________
>> 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/20160310/0b0de88e/attachment-0001.html 

From vivek.pandey at pinelabs.com  Thu Mar 10 05:59:46 2016
From: vivek.pandey at pinelabs.com (Vivek Pandey)
Date: Thu, 10 Mar 2016 16:29:46 +0530
Subject: [aerogear-dev] UPS 1.1.1.Final
In-Reply-To: <CAAg5f2QceJEkBS78-dVRUBhR5TC0aJwGhd9hQ46hcTj=CqruUQ@mail.gmail.com>
References: <CAAg5f2RJXMNeL9-UrQJUfcmXw9C5ix+sw1i0Q=GeQow5Q10QGA@mail.gmail.com>	<006d01d17ab4$0bb92500$232b6f00$@pinelabs.com>	<CAAg5f2TbiOv66HZAKvn_dnsvs62zTHR8DYHjdP=DWmG6ceo2Pw@mail.gmail.com>
	<CAAg5f2QceJEkBS78-dVRUBhR5TC0aJwGhd9hQ46hcTj=CqruUQ@mail.gmail.com>
Message-ID: <009401d17abb$f5b09b00$e111d100$@pinelabs.com>

Thanks Matthias, I have updated the bug with additional info I had.

 

From: mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] On Behalf Of Matthias Wessendorf
Sent: Thursday, March 10, 2016 4:18 PM
To: Vivek Pandey; AeroGear Developer Mailing List
Cc: aerogear-users at lists.jboss.org
Subject: Re: [aerogear-dev] UPS 1.1.1.Final

 

Looks like null is passed on the categories, for updating, the device metadata.

 

On it 

 

On Thu, Mar 10, 2016 at 11:40 AM, Matthias Wessendorf <matzew at apache.org> wrote:

can you add a few more details? how to reproduce this ? 

 

I will take a look

 

On Thu, Mar 10, 2016 at 11:03 AM, Vivek Pandey <vivek.pandey at pinelabs.com> wrote:

Great news!!

 

I can confirm that the bug I logged https://issues.jboss.org/browse/AGPUSH-1568 is fixed.

However, on upgradation I ran into another problem https://issues.jboss.org/browse/AGPUSH-1594

 

Thanks,

Vivek

 

From: aerogear-dev-bounces at lists.jboss.org [mailto:aerogear-dev-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf
Sent: Tuesday, March 08, 2016 2:31 PM
To: AeroGear Developer Mailing List; aerogear-users at lists.jboss.org
Subject: [aerogear-dev] UPS 1.1.1.Final

 

Hi,

 

the UPS 1.1.1.Final is now availabe!

https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.1.1.Final

 

Have fun!

 

-- 

Matthias Wessendorf 

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

 

  _____  

This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.

  _____  

 

 

_______________________________________________
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


This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160310/4fca161c/attachment.html 

From matzew at apache.org  Thu Mar 10 06:24:14 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 10 Mar 2016 12:24:14 +0100
Subject: [aerogear-dev] UPS 1.1.1.Final
In-Reply-To: <009401d17abb$f5b09b00$e111d100$@pinelabs.com>
References: <CAAg5f2RJXMNeL9-UrQJUfcmXw9C5ix+sw1i0Q=GeQow5Q10QGA@mail.gmail.com>
	<006d01d17ab4$0bb92500$232b6f00$@pinelabs.com>
	<CAAg5f2TbiOv66HZAKvn_dnsvs62zTHR8DYHjdP=DWmG6ceo2Pw@mail.gmail.com>
	<CAAg5f2QceJEkBS78-dVRUBhR5TC0aJwGhd9hQ46hcTj=CqruUQ@mail.gmail.com>
	<009401d17abb$f5b09b00$e111d100$@pinelabs.com>
Message-ID: <CAAg5f2QmEWDL-tZqPa9YFYoB7mGGx5B-eJ684L=ztJnnfjNqkA@mail.gmail.com>

Hi,

Vivek, can you check here?
https://github.com/aerogear/aerogear-unifiedpush-server/pull/686



On Thu, Mar 10, 2016 at 11:59 AM, Vivek Pandey <vivek.pandey at pinelabs.com>
wrote:

> Thanks Matthias, I have updated the bug with additional info I had.
>
>
>
> *From:* mwessendorf at gmail.com [mailto:mwessendorf at gmail.com] *On Behalf
> Of *Matthias Wessendorf
> *Sent:* Thursday, March 10, 2016 4:18 PM
> *To:* Vivek Pandey; AeroGear Developer Mailing List
> *Cc:* aerogear-users at lists.jboss.org
> *Subject:* Re: [aerogear-dev] UPS 1.1.1.Final
>
>
>
> Looks like null is passed on the categories, for updating, the device
> metadata.
>
>
>
> On it
>
>
>
> On Thu, Mar 10, 2016 at 11:40 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
> can you add a few more details? how to reproduce this ?
>
>
>
> I will take a look
>
>
>
> On Thu, Mar 10, 2016 at 11:03 AM, Vivek Pandey <vivek.pandey at pinelabs.com>
> wrote:
>
> Great news!!
>
>
>
> I can confirm that the bug I logged
> https://issues.jboss.org/browse/AGPUSH-1568 is fixed.
>
> However, on upgradation I ran into another problem
> https://issues.jboss.org/browse/AGPUSH-1594
>
>
>
> Thanks,
>
> Vivek
>
>
>
> *From:* aerogear-dev-bounces at lists.jboss.org [mailto:
> aerogear-dev-bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf
> *Sent:* Tuesday, March 08, 2016 2:31 PM
> *To:* AeroGear Developer Mailing List; aerogear-users at lists.jboss.org
> *Subject:* [aerogear-dev] UPS 1.1.1.Final
>
>
>
> Hi,
>
>
>
> the UPS 1.1.1.Final is now availabe!
>
>
> https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.1.1.Final
>
>
>
> Have fun!
>
>
>
> --
>
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> ------------------------------
>
> This message may contain privileged and confidential information and is
> solely for the use of intended recipient. The views expressed in this email
> are those of the sender and not of Pine Labs. The recipient should check
> this email and attachments for the presence of viruses / malwares etc. Pine
> Labs accepts no liability for any damage caused by any virus transmitted by
> this email. Pine Labs may monitor and record all emails.
> ------------------------------
>
>
>
>
>
> _______________________________________________
> 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
>
> ------------------------------
> This message may contain privileged and confidential information and is
> solely for the use of intended recipient. The views expressed in this email
> are those of the sender and not of Pine Labs. The recipient should check
> this email and attachments for the presence of viruses / malwares etc. Pine
> Labs accepts no liability for any damage caused by any virus transmitted by
> this email. Pine Labs may monitor and record all emails.
> ------------------------------
>
>


-- 
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/20160310/c1bce30b/attachment-0001.html 

From matzew at apache.org  Thu Mar 10 16:12:27 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 10 Mar 2016 22:12:27 +0100
Subject: [aerogear-dev] UPS 1.1.2: end of March-ish
Message-ID: <CAAg5f2Re12Mkzsf68s4m7jDj9qh4dm3+c3GcUMSPZr_=c=J_zQ@mail.gmail.com>

Hi,

we got a few fixes in this week, and I thought doing a 1.1.2 in a week or
two:
https://issues.jboss.org/projects/AGPUSH/versions/12329895

Any concerns ?

-- 
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/20160310/5c30bdea/attachment.html 

From matzew at apache.org  Thu Mar 10 17:09:55 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 10 Mar 2016 23:09:55 +0100
Subject: [aerogear-dev] Android/Cordova complaint
Message-ID: <CAAg5f2SOKTD+QhS0mOcfTVJS0XvEBJ8FB4DXLkqkvoddoiBYSw@mail.gmail.com>

Hi,

looks like an Ionic user is not too happy with the Cordova Plugin, on
Android:
https://forum.ionicframework.com/t/pushnotification-guide-for-android/3756/8

Any comments?

-- 
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/20160310/17f57d6f/attachment.html 

From supittma at redhat.com  Thu Mar 10 17:37:35 2016
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 10 Mar 2016 17:37:35 -0500
Subject: [aerogear-dev] Android/Cordova complaint
In-Reply-To: <CAAg5f2SOKTD+QhS0mOcfTVJS0XvEBJ8FB4DXLkqkvoddoiBYSw@mail.gmail.com>
References: <CAAg5f2SOKTD+QhS0mOcfTVJS0XvEBJ8FB4DXLkqkvoddoiBYSw@mail.gmail.com>
Message-ID: <CAEQz2CtLJFhx5+eyWsi3t0Z_=0HOt9bozFwq-XVV6BD7AUe-6Q@mail.gmail.com>

On Thu, Mar 10, 2016 at 5:09 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> looks like an Ionic user is not too happy with the Cordova Plugin, on
> Android:
>
> https://forum.ionicframework.com/t/pushnotification-guide-for-android/3756/8
>
> Any comments?
>

Looks like it is a cordova issue stemming from some of the bitrot happening
in Android.  I know for a fact we are very overdue for releasing a new
version of AGDroid tracking the latest changes in API levels, play services
sdks, etc.

Of course we are welcoming of PRs :)


>
> --
> 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/20160310/59811b56/attachment.html 

From matzew at apache.org  Thu Mar 10 17:43:20 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 10 Mar 2016 23:43:20 +0100
Subject: [aerogear-dev] Android/Cordova complaint
In-Reply-To: <CAEQz2CtLJFhx5+eyWsi3t0Z_=0HOt9bozFwq-XVV6BD7AUe-6Q@mail.gmail.com>
References: <CAAg5f2SOKTD+QhS0mOcfTVJS0XvEBJ8FB4DXLkqkvoddoiBYSw@mail.gmail.com>
	<CAEQz2CtLJFhx5+eyWsi3t0Z_=0HOt9bozFwq-XVV6BD7AUe-6Q@mail.gmail.com>
Message-ID: <CAAg5f2SYiR9R93s6S9Y=rGarkgKm2YWbcXqAos66y0gJmqifFA@mail.gmail.com>

On Thu, Mar 10, 2016 at 11:37 PM, Summers Pittman <supittma at redhat.com>
wrote:

>
>
> On Thu, Mar 10, 2016 at 5:09 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> looks like an Ionic user is not too happy with the Cordova Plugin, on
>> Android:
>>
>> https://forum.ionicframework.com/t/pushnotification-guide-for-android/3756/8
>>
>> Any comments?
>>
>
> Looks like it is a cordova issue stemming from some of the bitrot
> happening in Android.  I know for a fact we are very overdue for releasing
> a new version of AGDroid tracking the latest changes in API levels, play
> services sdks, etc.
>

+1 on the overdue. Mind creating a JIRA for updating the push lib (and it's
dependencies, pipe/core), w/ more recent APIs ?


>
> Of course we are welcoming of PRs :)
>

:-)


>
>
>>
>> --
>> 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/20160310/c7ea98df/attachment.html 

From supittma at redhat.com  Thu Mar 10 17:49:22 2016
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 10 Mar 2016 17:49:22 -0500
Subject: [aerogear-dev] Android/Cordova complaint
In-Reply-To: <CAAg5f2SYiR9R93s6S9Y=rGarkgKm2YWbcXqAos66y0gJmqifFA@mail.gmail.com>
References: <CAAg5f2SOKTD+QhS0mOcfTVJS0XvEBJ8FB4DXLkqkvoddoiBYSw@mail.gmail.com>
	<CAEQz2CtLJFhx5+eyWsi3t0Z_=0HOt9bozFwq-XVV6BD7AUe-6Q@mail.gmail.com>
	<CAAg5f2SYiR9R93s6S9Y=rGarkgKm2YWbcXqAos66y0gJmqifFA@mail.gmail.com>
Message-ID: <CAEQz2CtBo8jQLuSNcrTwJtktCzCDVD_8BKtgSfe4Pt5S9uCUbQ@mail.gmail.com>

On Thu, Mar 10, 2016 at 5:43 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Thu, Mar 10, 2016 at 11:37 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>>
>>
>> On Thu, Mar 10, 2016 at 5:09 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> looks like an Ionic user is not too happy with the Cordova Plugin, on
>>> Android:
>>>
>>> https://forum.ionicframework.com/t/pushnotification-guide-for-android/3756/8
>>>
>>> Any comments?
>>>
>>
>> Looks like it is a cordova issue stemming from some of the bitrot
>> happening in Android.  I know for a fact we are very overdue for releasing
>> a new version of AGDroid tracking the latest changes in API levels, play
>> services sdks, etc.
>>
>
> +1 on the overdue. Mind creating a JIRA for updating the push lib (and
> it's dependencies, pipe/core), w/ more recent APIs ?
>

I created a subtask on this JIRA :

https://issues.jboss.org/browse/AGDROID-427

There are also a suite of issues for updating the Android Maven plugin
which I am updating to just update all dependencies.


>
>
>>
>> Of course we are welcoming of PRs :)
>>
>
> :-)
>
>
>>
>>
>>>
>>> --
>>> 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
>
> _______________________________________________
> 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/20160310/9f646cd2/attachment-0001.html 

From supittma at redhat.com  Thu Mar 10 17:52:47 2016
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 10 Mar 2016 17:52:47 -0500
Subject: [aerogear-dev] Android/Cordova complaint
In-Reply-To: <CAEQz2CtBo8jQLuSNcrTwJtktCzCDVD_8BKtgSfe4Pt5S9uCUbQ@mail.gmail.com>
References: <CAAg5f2SOKTD+QhS0mOcfTVJS0XvEBJ8FB4DXLkqkvoddoiBYSw@mail.gmail.com>
	<CAEQz2CtLJFhx5+eyWsi3t0Z_=0HOt9bozFwq-XVV6BD7AUe-6Q@mail.gmail.com>
	<CAAg5f2SYiR9R93s6S9Y=rGarkgKm2YWbcXqAos66y0gJmqifFA@mail.gmail.com>
	<CAEQz2CtBo8jQLuSNcrTwJtktCzCDVD_8BKtgSfe4Pt5S9uCUbQ@mail.gmail.com>
Message-ID: <CAEQz2Ct9Bib-yrWH3HXCAW_vGrZGzwdw0HGaStjGzS+MbZ6TmQ@mail.gmail.com>

On Thu, Mar 10, 2016 at 5:49 PM, Summers Pittman <supittma at redhat.com>
wrote:

>
>
> On Thu, Mar 10, 2016 at 5:43 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Thu, Mar 10, 2016 at 11:37 PM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>>
>>>
>>> On Thu, Mar 10, 2016 at 5:09 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> looks like an Ionic user is not too happy with the Cordova Plugin, on
>>>> Android:
>>>>
>>>> https://forum.ionicframework.com/t/pushnotification-guide-for-android/3756/8
>>>>
>>>> Any comments?
>>>>
>>>
>>> Looks like it is a cordova issue stemming from some of the bitrot
>>> happening in Android.  I know for a fact we are very overdue for releasing
>>> a new version of AGDroid tracking the latest changes in API levels, play
>>> services sdks, etc.
>>>
>>
>> +1 on the overdue. Mind creating a JIRA for updating the push lib (and
>> it's dependencies, pipe/core), w/ more recent APIs ?
>>
>
> I created a subtask on this JIRA :
>
> https://issues.jboss.org/browse/AGDROID-427
>
> There are also a suite of issues for updating the Android Maven plugin
> which I am updating to just update all dependencies.
>

https://issues.jboss.org/browse/AGDROID-523 for an epic covering everyone.


>
>
>>
>>
>>>
>>> Of course we are welcoming of PRs :)
>>>
>>
>> :-)
>>
>>
>>>
>>>
>>>>
>>>> --
>>>> 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
>>
>> _______________________________________________
>> 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/20160310/58b6eed0/attachment.html 

From matzew at apache.org  Fri Mar 11 09:08:08 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 11 Mar 2016 15:08:08 +0100
Subject: [aerogear-dev] UPS 1.1.2: end of March-ish
In-Reply-To: <CAAg5f2Re12Mkzsf68s4m7jDj9qh4dm3+c3GcUMSPZr_=c=J_zQ@mail.gmail.com>
References: <CAAg5f2Re12Mkzsf68s4m7jDj9qh4dm3+c3GcUMSPZr_=c=J_zQ@mail.gmail.com>
Message-ID: <CAAg5f2Sz+zfNGxRL1TE9a5n7qMyiZxnw2YSU60dU2=226vHM4A@mail.gmail.com>

Also... why not having a 1.2.0-aplha.1 ?

https://issues.jboss.org/projects/AGPUSH/versions/12329905




On Thu, Mar 10, 2016 at 10:12 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> we got a few fixes in this week, and I thought doing a 1.1.2 in a week or
> two:
> https://issues.jboss.org/projects/AGPUSH/versions/12329895
>
> Any concerns ?
>
> --
> 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/20160311/9b4f5322/attachment.html 

From yanivn at c-b4.com  Tue Mar 15 03:22:37 2016
From: yanivn at c-b4.com (yaniv-cb4)
Date: Tue, 15 Mar 2016 00:22:37 -0700 (MST)
Subject: [aerogear-dev] C-B4 changes to Aerogear
Message-ID: <1458026557146-12395.post@n5.nabble.com>

Hi all, During the last 4-5 months C-B4 had made some  changes
<https://github.com/C-B4/unifiedpush-server/>   to AeroGear server.
I would like do discuss those changes with you guys in order to decide which
are relevant for aerogear upstream.

Technical issues, 
1) Maven changes to support Wildfly 8.2.1.
2) Maven eclipse integration, include js resources into output war.
3) unifiedpush-service - use arquillian/wildfly instead of openejb.
4) unifiedpush-jaxrs - additional tests using arquillian.

Feature changes:
1) Documents API - Store & Forward documents. Designed to support large
payload, store json doc and send silent push. 
2) Register installation in disabled mode. First step to versification
process.
3) Enable device based on verification process (SMS/Email). Plugable
architecture. default impl uses Clickatell API but can be configures to any
other vendor impl. 
4) Extended Multitenancy - Link aliases to application. First step to
section 5  
5) Move installation to new variant/application based on alias relation.



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/C-B4-changes-to-Aerogear-tp12395.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Tue Mar 15 03:39:25 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 15 Mar 2016 08:39:25 +0100
Subject: [aerogear-dev] C-B4 changes to Aerogear
In-Reply-To: <1458026557146-12395.post@n5.nabble.com>
References: <1458026557146-12395.post@n5.nabble.com>
Message-ID: <CAAg5f2RurZbfC1wjqWLNnjm5SdJJexrU08P7TzuZ3E5XSgkU-w@mail.gmail.com>

Hi Yaniv!

thanks for reaching out!

On Tue, Mar 15, 2016 at 8:22 AM, yaniv-cb4 <yanivn at c-b4.com> wrote:

> Hi all, During the last 4-5 months C-B4 had made some  changes
> <https://github.com/C-B4/unifiedpush-server/>   to AeroGear server.
> I would like do discuss those changes with you guys in order to decide
> which
> are relevant for aerogear upstream.
>
> Technical issues,
> 1) Maven changes to support Wildfly 8.2.1.
> 2) Maven eclipse integration, include js resources into output war.
> 3) unifiedpush-service - use arquillian/wildfly instead of openejb.
> 4) unifiedpush-jaxrs - additional tests using arquillian.
>

as indicated on our GH commit thread ([1]) over the last days, I am happy
to get all of these into our master branch :)



>
> Feature changes:
> 1) Documents API - Store & Forward documents. Designed to support large
> payload, store json doc and send silent push.
>

Sounds nice! This means a new/different sender API was added for sending
large payload (too large for iOS (e.g. bigger than 2k))?
The payload is stored on the UPS DB and can be fetched by the devices (e.g.
after a silent push) via HTTP basic? Or are these "fetch" routes Keycloak
protected?




> 2) Register installation in disabled mode. First step to versification
> process.
> 3) Enable device based on verification process (SMS/Email). Plugable
> architecture. default impl uses Clickatell API but can be configures to any
> other vendor impl.
>

Ah, this is nice feature as well. By default (or per setting), all devices
are initially disabled for push, right? Via successful SMS/EMail
verification the push will be enabled for the device?

I do like this and can see interest in this at our community. Glad to see
the architecture is plugable, because I am not too thrilled about
hard-coded dependencies against some proprietary SMS API. How can the
actual SMS (or Email) implementation be enabled/configured?



> 4) Extended Multitenancy - Link aliases to application. First step to
> section 5
> 5) Move installation to new variant/application based on alias relation.
>
>
Can you explain a bit more on this e.g. what's the use-case here ?

Thanks again for reaching out!


Cheers,
Matthias


[1]
https://github.com/C-B4/unifiedpush-server/commit/4a80602fdbf2121d867187d619bda03a7472758a#commitcomment-16629453





>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/C-B4-changes-to-Aerogear-tp12395.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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160315/2112a2e0/attachment-0001.html 

From lukas.fryc at gmail.com  Tue Mar 15 07:56:48 2016
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Tue, 15 Mar 2016 12:56:48 +0100
Subject: [aerogear-dev] GCM Topics in UPS
In-Reply-To: <CAEQz2Cti4=9aTTojXAwGsZi=itWpO5i9F9DgHLuS2UV1XbsQ6w@mail.gmail.com>
References: <CAEQz2CtQLhHJOxNO5qbOMyjjzV9jne_O3Lo7Z56vrMNFuY=6LQ@mail.gmail.com>
	<CAD_dpu233utue3k6fC+CiNoSEhe+0o9mpXF67AK6LYzFMUqz=A@mail.gmail.com>
	<CAEQz2Cti4=9aTTojXAwGsZi=itWpO5i9F9DgHLuS2UV1XbsQ6w@mail.gmail.com>
Message-ID: <CAEroY34vsgtD2OOvb1g7gVn2PHuc6t54Mbo7X+=nbyNo+xBmyg@mail.gmail.com>

Continuing on this discussion,

I remember we have met with Summers around this idea to identify what we
can expect from GCM Topics when considering how UPS works internally with
message queues.

The ideal implementation as Summers suggested is to try pushing via a GCM
Topic and if push can't be performed this way, fall back to device-token
based push.


In terms of UPS/JMS, I believe we should split GCM traffic into two queues:


   - GCMTokenBatchQueue
   - GCMTopicQueue

You can use this diagram to get better idea:
https://docs.google.com/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_EXQMYYr_jcu7nFmE/edit


Then the algorithm can be drawn as:

1. TokenLoader will identify categories/topics it can use to optimize GCM
message dispatching - it will push appropriate GCMTopicQueue events and
potentially send also GCMTokenBatchQueue events for devices that are not
covered by GCM topics

2. TokenLoader should also perform DB count for each category/topic, and if
it should go beyond 1 million tokens limit, it falls back to use device
tokens

3. if for any reason the push to GCM topic fails we can still expand device
tokens - in that case the only implementation detail is that we don't know
whether device tokens are all loaded until all topic-based messages are
processed


On Tue, Jul 28, 2015 at 4:40 PM, Summers Pittman <supittma at redhat.com>
wrote:

>
>
> On Tue, Jul 28, 2015 at 10:20 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> Yo !
>> I have not enough info on the GCM Topic stuff but reading your message it
>> sounds that we should leverage this "transparently" for the user , meaning
>> it just uses the UPS categories and under the hood we use the GCM topics
>> stuff.
>> Like you said we have to handle the fall over if they are more than 1
>> million user but since we use JMS batches with counting that should not be
>> too hard (but Lukas should be able to give us more info on that)
>>
> Awesome.  I'll run ahead with my ideas then and let people hash out their
> merits in the PR.
>
>>
>>
>> On Mon, Jul 27, 2015 at 5:22 PM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>> So I've got a few ideas for how to implement this, but I hope some
>>> people more experienced with the platform can give some feedback before.
>>>
>>> Quick Background:
>>> In UPS right now we have a concept of categories.  A single UPS message
>>> can be broadcast to a bunch of devices which are subscribed to this
>>> category.  Google now supports this for GCM on Chrome, iOS, and Android so
>>> UPS can send a single message to GCM and GCM will broadcast that to up to a
>>> million devices.
>>> End Quick Background
>>>
>>> So first, how do we switch between sending a message to each device in a
>>> category to sending a topic message to GCM?
>>>
>>> In TokenLoader.java#L113 we are using the clientInstallationService to
>>> build a string of deviceTokens based on the variant and message criteria.
>>> Is there any reason we can't create a "topicToken" which will be recognized
>>> later by GCMPushNotificationSender?  Another benefit to making this change
>>> here is that if we have over a million subscribers to the category we can
>>> just default to the default messaging.
>>>
>>> There is also an open issue of whether or not we will update the clients
>>> to filter based on what category a message was sent to.  To do this we will
>>> have to include the category information in the message when we send it to
>>> devices going forward.  In GCM a topic message includes this information.
>>> This means that if we have over a million subscriptions in the topic we
>>> will need to fall back to using the category information anyway.
>>>
>>> Continuing on from the thread of falling back, it is possible for a
>>> topic message to fail to send because there are too many subscribers.  How
>>> would UPS handle regenerating the messages as deviceToken instead of
>>> topicToken messages?
>>>
>>> Of course if someone has a better idea than "topicTokens" I'm all ears.
>>>
>>>
>>> _______________________________________________
>>> 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/20160315/fd3ba256/attachment.html 

From idel.pivnitskiy at gmail.com  Tue Mar 15 16:17:27 2016
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Tue, 15 Mar 2016 23:17:27 +0300
Subject: [aerogear-dev] AeroGear WebPush Java Client
In-Reply-To: <CAN+BUJo2V08gp0E7Kn-dCLABpHbe4+-ghY8wF2v5XxSD8_PLPQ@mail.gmail.com>
References: <CAN+BUJo2V08gp0E7Kn-dCLABpHbe4+-ghY8wF2v5XxSD8_PLPQ@mail.gmail.com>
Message-ID: <CAN+BUJoMdr=EV4nn6k3aE7w8mshkN54bWSf8_F2tJ0YAcUbYRg@mail.gmail.com>

What's new in WebPush Java Client:

   - Updated to the latest aerogear-parent
   - Updated Jetty http2-client to the latest version
   - Clean up pom.xml
   - Subscription and PushMessage objects became to be Serializable
   - Refactoring and little improvements
   - Added documentation to all public classes and methods - the most
   valuable improvement :)

For more information, see [1].

Tests will be coming soon...

[1]
https://github.com/idelpivnitskiy/aerogear-webpush-java-client/commits/master

Best regards,
Idel Pivnitskiy
--
Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>

On Wed, Aug 19, 2015 at 7:30 AM, Idel Pivnitskiy <idel.pivnitskiy at gmail.com>
wrote:

> Hi all!
>
> I've just implemented a lightweight java client for receiving push
> messages from AeroGear WebPush Server [1]. It is easy to use and fully
> async!
>
> A few words about decision to use Jetty as a HTTP/2 client:
>
> Currently there are only 3 Java libraries, which implement client side of
> HTTP/2 protocol [2]: Netty, Jetty and OkHttp. I tried all of them:
>
>    - First of all I tried to use OkHttp. This is a lightweight http
>    client for Android and other Java apps. But currently this library supports
>    HTTP/2 protocol only via old HTTP/1.1 API. It works well for simple
>    request-response, but its client API does not allow to use HTTP/2 features,
>    like Server Push Frames. I looked at GRPC [3], because Googlers use OkHttp
>    for HTTP/2 transport. But they don't use public API, they use only inner
>    classes to handle frames and built their own logic atop this classes. It
>    would be too complicated for our purposes.
>    - Secondary, I tried to refactor our WebPush console to a client
>    library. But this way is complicated too. netty-codec-http2 does not
>    provide a client API, it is only codec, low level protocol implementation.
>    - Now I use jetty-http2-client. It is easy to configure and use, fast
>    and async. Jetty provides a user friendly API to handle HTTP/2 streams and
>    get PUSH_PROMISE frames.
>
> For more information, look at my commit history.
> In the future, if there will be more lightweight alternatives than Jetty
> (for example, new version of OkHttp or Java 9 API), I will rewrite the
> transport layer of my library.
>
> Here is an example, how to use my library [4].
>
> [1] https://github.com/idelpivnitskiy/aerogear-webpush-java-client
> [2] https://github.com/http2/http2-spec/wiki/Implementations
> [3] https://github.com/grpc/grpc-java/tree/master/okhttp
> [4]
> https://github.com/idelpivnitskiy/aerogear-webpush-java-client/blob/master/src/example/java/org/jboss/aerogear/webpush/Example.java
>
> Best regards,
> Idel Pivnitskiy
> --
> E-mail: Idel.Pivnitskiy at gmail.com
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160315/d0bcdecc/attachment.html 

From edewit at redhat.com  Wed Mar 16 03:14:20 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Wed, 16 Mar 2016 08:14:20 +0100
Subject: [aerogear-dev] AeroGear WebPush Java Client
In-Reply-To: <CAN+BUJoMdr=EV4nn6k3aE7w8mshkN54bWSf8_F2tJ0YAcUbYRg@mail.gmail.com>
References: <CAN+BUJo2V08gp0E7Kn-dCLABpHbe4+-ghY8wF2v5XxSD8_PLPQ@mail.gmail.com>
	<CAN+BUJoMdr=EV4nn6k3aE7w8mshkN54bWSf8_F2tJ0YAcUbYRg@mail.gmail.com>
Message-ID: <CAO2B-fYaUzqfOyEk5iLO3e3rNSQHxBekK5ehJW0W8zMzRLDaoA@mail.gmail.com>

will this replace the java client [1] we currently have? Or will can we
extend it?

[1] https://github.com/aerogear/aerogear-simplepush-java-client

On Tue, Mar 15, 2016 at 9:17 PM, Idel Pivnitskiy <idel.pivnitskiy at gmail.com>
wrote:

> What's new in WebPush Java Client:
>
>    - Updated to the latest aerogear-parent
>    - Updated Jetty http2-client to the latest version
>    - Clean up pom.xml
>    - Subscription and PushMessage objects became to be Serializable
>    - Refactoring and little improvements
>    - Added documentation to all public classes and methods - the most
>    valuable improvement :)
>
> For more information, see [1].
>
> Tests will be coming soon...
>
> [1]
> https://github.com/idelpivnitskiy/aerogear-webpush-java-client/commits/master
>
> Best regards,
> Idel Pivnitskiy
> --
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>
> On Wed, Aug 19, 2015 at 7:30 AM, Idel Pivnitskiy <
> idel.pivnitskiy at gmail.com> wrote:
>
>> Hi all!
>>
>> I've just implemented a lightweight java client for receiving push
>> messages from AeroGear WebPush Server [1]. It is easy to use and fully
>> async!
>>
>> A few words about decision to use Jetty as a HTTP/2 client:
>>
>> Currently there are only 3 Java libraries, which implement client side of
>> HTTP/2 protocol [2]: Netty, Jetty and OkHttp. I tried all of them:
>>
>>    - First of all I tried to use OkHttp. This is a lightweight http
>>    client for Android and other Java apps. But currently this library supports
>>    HTTP/2 protocol only via old HTTP/1.1 API. It works well for simple
>>    request-response, but its client API does not allow to use HTTP/2 features,
>>    like Server Push Frames. I looked at GRPC [3], because Googlers use OkHttp
>>    for HTTP/2 transport. But they don't use public API, they use only inner
>>    classes to handle frames and built their own logic atop this classes. It
>>    would be too complicated for our purposes.
>>    - Secondary, I tried to refactor our WebPush console to a client
>>    library. But this way is complicated too. netty-codec-http2 does not
>>    provide a client API, it is only codec, low level protocol implementation.
>>    - Now I use jetty-http2-client. It is easy to configure and use, fast
>>    and async. Jetty provides a user friendly API to handle HTTP/2 streams and
>>    get PUSH_PROMISE frames.
>>
>> For more information, look at my commit history.
>> In the future, if there will be more lightweight alternatives than Jetty
>> (for example, new version of OkHttp or Java 9 API), I will rewrite the
>> transport layer of my library.
>>
>> Here is an example, how to use my library [4].
>>
>> [1] https://github.com/idelpivnitskiy/aerogear-webpush-java-client
>> [2] https://github.com/http2/http2-spec/wiki/Implementations
>> [3] https://github.com/grpc/grpc-java/tree/master/okhttp
>> [4]
>> https://github.com/idelpivnitskiy/aerogear-webpush-java-client/blob/master/src/example/java/org/jboss/aerogear/webpush/Example.java
>>
>> Best regards,
>> Idel Pivnitskiy
>> --
>> E-mail: Idel.Pivnitskiy at gmail.com
>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>>
>
>
> _______________________________________________
> 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/20160316/f2010f73/attachment-0001.html 

From matzew at apache.org  Wed Mar 16 03:46:26 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 16 Mar 2016 08:46:26 +0100
Subject: [aerogear-dev] AeroGear WebPush Java Client
In-Reply-To: <CAN+BUJoMdr=EV4nn6k3aE7w8mshkN54bWSf8_F2tJ0YAcUbYRg@mail.gmail.com>
References: <CAN+BUJo2V08gp0E7Kn-dCLABpHbe4+-ghY8wF2v5XxSD8_PLPQ@mail.gmail.com>
	<CAN+BUJoMdr=EV4nn6k3aE7w8mshkN54bWSf8_F2tJ0YAcUbYRg@mail.gmail.com>
Message-ID: <CAAg5f2Qrrkrg7yJz5LuXHzUD0cbEYBNpFa1A-dC=Pxfp=fWVjQ@mail.gmail.com>

awesome!

wanna have it included in the aerogear organization ?

On Tue, Mar 15, 2016 at 9:17 PM, Idel Pivnitskiy <idel.pivnitskiy at gmail.com>
wrote:

> What's new in WebPush Java Client:
>
>    - Updated to the latest aerogear-parent
>    - Updated Jetty http2-client to the latest version
>    - Clean up pom.xml
>    - Subscription and PushMessage objects became to be Serializable
>    - Refactoring and little improvements
>    - Added documentation to all public classes and methods - the most
>    valuable improvement :)
>
> For more information, see [1].
>
> Tests will be coming soon...
>
> [1]
> https://github.com/idelpivnitskiy/aerogear-webpush-java-client/commits/master
>
> Best regards,
> Idel Pivnitskiy
> --
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>
> On Wed, Aug 19, 2015 at 7:30 AM, Idel Pivnitskiy <
> idel.pivnitskiy at gmail.com> wrote:
>
>> Hi all!
>>
>> I've just implemented a lightweight java client for receiving push
>> messages from AeroGear WebPush Server [1]. It is easy to use and fully
>> async!
>>
>> A few words about decision to use Jetty as a HTTP/2 client:
>>
>> Currently there are only 3 Java libraries, which implement client side of
>> HTTP/2 protocol [2]: Netty, Jetty and OkHttp. I tried all of them:
>>
>>    - First of all I tried to use OkHttp. This is a lightweight http
>>    client for Android and other Java apps. But currently this library supports
>>    HTTP/2 protocol only via old HTTP/1.1 API. It works well for simple
>>    request-response, but its client API does not allow to use HTTP/2 features,
>>    like Server Push Frames. I looked at GRPC [3], because Googlers use OkHttp
>>    for HTTP/2 transport. But they don't use public API, they use only inner
>>    classes to handle frames and built their own logic atop this classes. It
>>    would be too complicated for our purposes.
>>    - Secondary, I tried to refactor our WebPush console to a client
>>    library. But this way is complicated too. netty-codec-http2 does not
>>    provide a client API, it is only codec, low level protocol implementation.
>>    - Now I use jetty-http2-client. It is easy to configure and use, fast
>>    and async. Jetty provides a user friendly API to handle HTTP/2 streams and
>>    get PUSH_PROMISE frames.
>>
>> For more information, look at my commit history.
>> In the future, if there will be more lightweight alternatives than Jetty
>> (for example, new version of OkHttp or Java 9 API), I will rewrite the
>> transport layer of my library.
>>
>> Here is an example, how to use my library [4].
>>
>> [1] https://github.com/idelpivnitskiy/aerogear-webpush-java-client
>> [2] https://github.com/http2/http2-spec/wiki/Implementations
>> [3] https://github.com/grpc/grpc-java/tree/master/okhttp
>> [4]
>> https://github.com/idelpivnitskiy/aerogear-webpush-java-client/blob/master/src/example/java/org/jboss/aerogear/webpush/Example.java
>>
>> Best regards,
>> Idel Pivnitskiy
>> --
>> E-mail: Idel.Pivnitskiy at gmail.com
>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>> GitHub: @idelpivnitskiy <https://github.com/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/20160316/5bd84537/attachment.html 

From idel.pivnitskiy at gmail.com  Wed Mar 16 05:34:20 2016
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Wed, 16 Mar 2016 12:34:20 +0300
Subject: [aerogear-dev] AeroGear WebPush Java Client
In-Reply-To: <CAAg5f2Qrrkrg7yJz5LuXHzUD0cbEYBNpFa1A-dC=Pxfp=fWVjQ@mail.gmail.com>
References: <CAN+BUJo2V08gp0E7Kn-dCLABpHbe4+-ghY8wF2v5XxSD8_PLPQ@mail.gmail.com>
	<CAN+BUJoMdr=EV4nn6k3aE7w8mshkN54bWSf8_F2tJ0YAcUbYRg@mail.gmail.com>
	<CAAg5f2Qrrkrg7yJz5LuXHzUD0cbEYBNpFa1A-dC=Pxfp=fWVjQ@mail.gmail.com>
Message-ID: <CAN+BUJqjEDxVT+XjBCairJzeM++c2i1yYgBXw9SjY3xa_LmPdQ@mail.gmail.com>

>
> will this replace the java client [1] we currently have? Or will can we
> extend it?


Think that it will replace SimplePush in the future.

wanna have it included in the aerogear organization ?


it would be great :)

Best regards,
Idel Pivnitskiy
--
Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>

On Wed, Mar 16, 2016 at 10:46 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> awesome!
>
> wanna have it included in the aerogear organization ?
>
> On Tue, Mar 15, 2016 at 9:17 PM, Idel Pivnitskiy <
> idel.pivnitskiy at gmail.com> wrote:
>
>> What's new in WebPush Java Client:
>>
>>    - Updated to the latest aerogear-parent
>>    - Updated Jetty http2-client to the latest version
>>    - Clean up pom.xml
>>    - Subscription and PushMessage objects became to be Serializable
>>    - Refactoring and little improvements
>>    - Added documentation to all public classes and methods - the most
>>    valuable improvement :)
>>
>> For more information, see [1].
>>
>> Tests will be coming soon...
>>
>> [1]
>> https://github.com/idelpivnitskiy/aerogear-webpush-java-client/commits/master
>>
>> Best regards,
>> Idel Pivnitskiy
>> --
>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>>
>> On Wed, Aug 19, 2015 at 7:30 AM, Idel Pivnitskiy <
>> idel.pivnitskiy at gmail.com> wrote:
>>
>>> Hi all!
>>>
>>> I've just implemented a lightweight java client for receiving push
>>> messages from AeroGear WebPush Server [1]. It is easy to use and fully
>>> async!
>>>
>>> A few words about decision to use Jetty as a HTTP/2 client:
>>>
>>> Currently there are only 3 Java libraries, which implement client side
>>> of HTTP/2 protocol [2]: Netty, Jetty and OkHttp. I tried all of them:
>>>
>>>    - First of all I tried to use OkHttp. This is a lightweight http
>>>    client for Android and other Java apps. But currently this library supports
>>>    HTTP/2 protocol only via old HTTP/1.1 API. It works well for simple
>>>    request-response, but its client API does not allow to use HTTP/2 features,
>>>    like Server Push Frames. I looked at GRPC [3], because Googlers use OkHttp
>>>    for HTTP/2 transport. But they don't use public API, they use only inner
>>>    classes to handle frames and built their own logic atop this classes. It
>>>    would be too complicated for our purposes.
>>>    - Secondary, I tried to refactor our WebPush console to a client
>>>    library. But this way is complicated too. netty-codec-http2 does not
>>>    provide a client API, it is only codec, low level protocol implementation.
>>>    - Now I use jetty-http2-client. It is easy to configure and use,
>>>    fast and async. Jetty provides a user friendly API to handle HTTP/2 streams
>>>    and get PUSH_PROMISE frames.
>>>
>>> For more information, look at my commit history.
>>> In the future, if there will be more lightweight alternatives than Jetty
>>> (for example, new version of OkHttp or Java 9 API), I will rewrite the
>>> transport layer of my library.
>>>
>>> Here is an example, how to use my library [4].
>>>
>>> [1] https://github.com/idelpivnitskiy/aerogear-webpush-java-client
>>> [2] https://github.com/http2/http2-spec/wiki/Implementations
>>> [3] https://github.com/grpc/grpc-java/tree/master/okhttp
>>> [4]
>>> https://github.com/idelpivnitskiy/aerogear-webpush-java-client/blob/master/src/example/java/org/jboss/aerogear/webpush/Example.java
>>>
>>> Best regards,
>>> Idel Pivnitskiy
>>> --
>>> E-mail: Idel.Pivnitskiy at gmail.com
>>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>>> GitHub: @idelpivnitskiy <https://github.com/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
>
> _______________________________________________
> 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/20160316/89b7a3ac/attachment.html 

From matzew at apache.org  Wed Mar 16 16:52:44 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 16 Mar 2016 21:52:44 +0100
Subject: [aerogear-dev] AeroGear WebPush Java Client
In-Reply-To: <CAN+BUJqjEDxVT+XjBCairJzeM++c2i1yYgBXw9SjY3xa_LmPdQ@mail.gmail.com>
References: <CAN+BUJo2V08gp0E7Kn-dCLABpHbe4+-ghY8wF2v5XxSD8_PLPQ@mail.gmail.com>
	<CAN+BUJoMdr=EV4nn6k3aE7w8mshkN54bWSf8_F2tJ0YAcUbYRg@mail.gmail.com>
	<CAAg5f2Qrrkrg7yJz5LuXHzUD0cbEYBNpFa1A-dC=Pxfp=fWVjQ@mail.gmail.com>
	<CAN+BUJqjEDxVT+XjBCairJzeM++c2i1yYgBXw9SjY3xa_LmPdQ@mail.gmail.com>
Message-ID: <CAAg5f2SNP3eErf3FDE8k63-JpHS1dje-aEhZT3nZ27j+GHOuMg@mail.gmail.com>

Having this client allows us a better integration of WebPush into UPS, at
some point (I need to check the javaagent for WildFly's bootclasspath
anyways for my PoC on APNs' HTTP/2 APIs, like [1]).

However, I was wondering how 'up-to-date' our server actually is, regarding
the spec



[1] http://undertow.io/blog/2015/03/26/HTTP2-In-Wildfly.html

On Wed, Mar 16, 2016 at 10:34 AM, Idel Pivnitskiy <idel.pivnitskiy at gmail.com
> wrote:

> will this replace the java client [1] we currently have? Or will can we
>> extend it?
>
>
> Think that it will replace SimplePush in the future.
>
> wanna have it included in the aerogear organization ?
>
>
> it would be great :)
>
> Best regards,
> Idel Pivnitskiy
> --
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>
> On Wed, Mar 16, 2016 at 10:46 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> awesome!
>>
>> wanna have it included in the aerogear organization ?
>>
>> On Tue, Mar 15, 2016 at 9:17 PM, Idel Pivnitskiy <
>> idel.pivnitskiy at gmail.com> wrote:
>>
>>> What's new in WebPush Java Client:
>>>
>>>    - Updated to the latest aerogear-parent
>>>    - Updated Jetty http2-client to the latest version
>>>    - Clean up pom.xml
>>>    - Subscription and PushMessage objects became to be Serializable
>>>    - Refactoring and little improvements
>>>    - Added documentation to all public classes and methods - the most
>>>    valuable improvement :)
>>>
>>> For more information, see [1].
>>>
>>> Tests will be coming soon...
>>>
>>> [1]
>>> https://github.com/idelpivnitskiy/aerogear-webpush-java-client/commits/master
>>>
>>> Best regards,
>>> Idel Pivnitskiy
>>> --
>>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>>> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>>>
>>> On Wed, Aug 19, 2015 at 7:30 AM, Idel Pivnitskiy <
>>> idel.pivnitskiy at gmail.com> wrote:
>>>
>>>> Hi all!
>>>>
>>>> I've just implemented a lightweight java client for receiving push
>>>> messages from AeroGear WebPush Server [1]. It is easy to use and fully
>>>> async!
>>>>
>>>> A few words about decision to use Jetty as a HTTP/2 client:
>>>>
>>>> Currently there are only 3 Java libraries, which implement client side
>>>> of HTTP/2 protocol [2]: Netty, Jetty and OkHttp. I tried all of them:
>>>>
>>>>    - First of all I tried to use OkHttp. This is a lightweight http
>>>>    client for Android and other Java apps. But currently this library supports
>>>>    HTTP/2 protocol only via old HTTP/1.1 API. It works well for simple
>>>>    request-response, but its client API does not allow to use HTTP/2 features,
>>>>    like Server Push Frames. I looked at GRPC [3], because Googlers use OkHttp
>>>>    for HTTP/2 transport. But they don't use public API, they use only inner
>>>>    classes to handle frames and built their own logic atop this classes. It
>>>>    would be too complicated for our purposes.
>>>>    - Secondary, I tried to refactor our WebPush console to a client
>>>>    library. But this way is complicated too. netty-codec-http2 does not
>>>>    provide a client API, it is only codec, low level protocol implementation.
>>>>    - Now I use jetty-http2-client. It is easy to configure and use,
>>>>    fast and async. Jetty provides a user friendly API to handle HTTP/2 streams
>>>>    and get PUSH_PROMISE frames.
>>>>
>>>> For more information, look at my commit history.
>>>> In the future, if there will be more lightweight alternatives than
>>>> Jetty (for example, new version of OkHttp or Java 9 API), I will rewrite
>>>> the transport layer of my library.
>>>>
>>>> Here is an example, how to use my library [4].
>>>>
>>>> [1] https://github.com/idelpivnitskiy/aerogear-webpush-java-client
>>>> [2] https://github.com/http2/http2-spec/wiki/Implementations
>>>> [3] https://github.com/grpc/grpc-java/tree/master/okhttp
>>>> [4]
>>>> https://github.com/idelpivnitskiy/aerogear-webpush-java-client/blob/master/src/example/java/org/jboss/aerogear/webpush/Example.java
>>>>
>>>> Best regards,
>>>> Idel Pivnitskiy
>>>> --
>>>> E-mail: Idel.Pivnitskiy at gmail.com
>>>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>>>> GitHub: @idelpivnitskiy <https://github.com/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
>>
>> _______________________________________________
>> 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/20160316/b2d0e7d2/attachment-0001.html 

From lukas at fryc.eu  Fri Mar 18 04:31:56 2016
From: lukas at fryc.eu (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Fri, 18 Mar 2016 09:31:56 +0100
Subject: [aerogear-dev] UPS 1.2.0+ on WF10/JDK8 - should we continue
	supporting WF8/JDK7?
Message-ID: <CAEroY35Gw8=d09XorWcyramB9xRrFuEDLK23MS-AYFEbn=RQYA@mail.gmail.com>

Hi guys,

we are working on delivering some improvements in UPS messaging subsystem
in 1.2.0,

and part of that is also adoption of WF10 (with ActiveMQ Artemis
underneath).


The problem is that WF10 is JDK8 only, so if we use it for tests, we are
limiting ourselves to JDK8-only build. We could run it on WF8 with JDK7,
off course.

Question is, do we want to support WF8 with UPS 1.2.0+, or should we switch
to WF10 only?


Cheers,

~ Lukas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160318/e1bd672c/attachment.html 

From lukas.fryc at gmail.com  Fri Mar 18 04:33:17 2016
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Fri, 18 Mar 2016 09:33:17 +0100
Subject: [aerogear-dev] UPS 1.2.0+ on WF10/JDK8 - should we continue
	supporting WF8/JDK7?
Message-ID: <CAEroY371sqfHSMxFzq=y7K1qT6SsCZAGpS1nW9A8q_jPqM2+6A@mail.gmail.com>

Hi guys,

we are working on delivering some improvements in UPS messaging subsystem
in 1.2.0,

and part of that is also adoption of WF10 (with ActiveMQ Artemis
underneath).


The problem is that WF10 is JDK8 only, so if we use it for tests, we are
limiting ourselves to JDK8-only build. We could run it on WF8 with JDK7,
off course.

Question is, do we want to support WF8 with UPS 1.2.0+, or should we switch
to WF10 only?


Cheers,

~ Lukas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160318/78c0ed91/attachment.html 

From matzew at apache.org  Fri Mar 18 04:34:42 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 18 Mar 2016 09:34:42 +0100
Subject: [aerogear-dev] UPS 1.2.0+ on WF10/JDK8 - should we continue
 supporting WF8/JDK7?
In-Reply-To: <CAEroY35Gw8=d09XorWcyramB9xRrFuEDLK23MS-AYFEbn=RQYA@mail.gmail.com>
References: <CAEroY35Gw8=d09XorWcyramB9xRrFuEDLK23MS-AYFEbn=RQYA@mail.gmail.com>
Message-ID: <CAAg5f2QQ=u3=kaSpc2gWwm62fWYg=ZKHxDaiK8xrdkcw=LOKug@mail.gmail.com>

For our work, required for supporting APNs' HTTP/2 APIs we also need JDK-8.

I wonder if we should call the release 2.0.0, and really aim only WF10/EAP7
+ (Open)JDK-8

On Fri, Mar 18, 2016 at 9:31 AM, Luk?? Fry? <lukas at fryc.eu> wrote:

> Hi guys,
>
> we are working on delivering some improvements in UPS messaging subsystem
> in 1.2.0,
>
> and part of that is also adoption of WF10 (with ActiveMQ Artemis
> underneath).
>
>
> The problem is that WF10 is JDK8 only, so if we use it for tests, we are
> limiting ourselves to JDK8-only build. We could run it on WF8 with JDK7,
> off course.
>
> Question is, do we want to support WF8 with UPS 1.2.0+, or should we
> switch to WF10 only?
>
>
> Cheers,
>
> ~ Lukas
>
> _______________________________________________
> 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/20160318/b5f57540/attachment.html 

From matzew at apache.org  Fri Mar 18 04:41:10 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 18 Mar 2016 09:41:10 +0100
Subject: [aerogear-dev] UPS 1.2.0+ on WF10/JDK8 - should we continue
 supporting WF8/JDK7?
In-Reply-To: <CAAg5f2QQ=u3=kaSpc2gWwm62fWYg=ZKHxDaiK8xrdkcw=LOKug@mail.gmail.com>
References: <CAEroY35Gw8=d09XorWcyramB9xRrFuEDLK23MS-AYFEbn=RQYA@mail.gmail.com>
	<CAAg5f2QQ=u3=kaSpc2gWwm62fWYg=ZKHxDaiK8xrdkcw=LOKug@mail.gmail.com>
Message-ID: <CAAg5f2Sy1mQodv1Jg=RgfrcWfMp3yWxUXMBrQZxREsX0nHnCGw@mail.gmail.com>

Another thing is, Keycloak also is now JDK-8:
https://github.com/keycloak/keycloak/tree/1.8.1.Final#building

(current release is 1.9.1 and 2.0.0-CR1 is in the making)

And one of the JDKs even called Java7 dead, sure... that's not that
important.

I am very supportive of this, especially our main server platforms (WildFly
and EAP) are also Java8 only with the latest releases



On Fri, Mar 18, 2016 at 9:34 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> For our work, required for supporting APNs' HTTP/2 APIs we also need JDK-8.
>
> I wonder if we should call the release 2.0.0, and really aim only
> WF10/EAP7 + (Open)JDK-8
>
> On Fri, Mar 18, 2016 at 9:31 AM, Luk?? Fry? <lukas at fryc.eu> wrote:
>
>> Hi guys,
>>
>> we are working on delivering some improvements in UPS messaging subsystem
>> in 1.2.0,
>>
>> and part of that is also adoption of WF10 (with ActiveMQ Artemis
>> underneath).
>>
>>
>> The problem is that WF10 is JDK8 only, so if we use it for tests, we are
>> limiting ourselves to JDK8-only build. We could run it on WF8 with JDK7,
>> off course.
>>
>> Question is, do we want to support WF8 with UPS 1.2.0+, or should we
>> switch to WF10 only?
>>
>>
>> Cheers,
>>
>> ~ Lukas
>>
>> _______________________________________________
>> 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/20160318/915834dc/attachment.html 

From idel.pivnitskiy at gmail.com  Fri Mar 18 05:07:01 2016
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Fri, 18 Mar 2016 12:07:01 +0300
Subject: [aerogear-dev] UPS 1.2.0+ on WF10/JDK8 - should we continue
 supporting WF8/JDK7?
In-Reply-To: <CAAg5f2Sy1mQodv1Jg=RgfrcWfMp3yWxUXMBrQZxREsX0nHnCGw@mail.gmail.com>
References: <CAEroY35Gw8=d09XorWcyramB9xRrFuEDLK23MS-AYFEbn=RQYA@mail.gmail.com>
	<CAAg5f2QQ=u3=kaSpc2gWwm62fWYg=ZKHxDaiK8xrdkcw=LOKug@mail.gmail.com>
	<CAAg5f2Sy1mQodv1Jg=RgfrcWfMp3yWxUXMBrQZxREsX0nHnCGw@mail.gmail.com>
Message-ID: <CAN+BUJpSbnQC8RSzvLsBqMju-Y=jv8+XvZJXCG-pvj4e=1Gcxg@mail.gmail.com>

+1 that release which works only with JDK-8 and WF10 should be called 2.0.0

+2 that time to move to JDK-8 :) of course if we don't have special
requirements to support JDK-7

Best regards,
Idel Pivnitskiy
--
Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>

On Fri, Mar 18, 2016 at 11:41 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Another thing is, Keycloak also is now JDK-8:
> https://github.com/keycloak/keycloak/tree/1.8.1.Final#building
>
> (current release is 1.9.1 and 2.0.0-CR1 is in the making)
>
> And one of the JDKs even called Java7 dead, sure... that's not that
> important.
>
> I am very supportive of this, especially our main server platforms
> (WildFly and EAP) are also Java8 only with the latest releases
>
>
>
> On Fri, Mar 18, 2016 at 9:34 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> For our work, required for supporting APNs' HTTP/2 APIs we also need
>> JDK-8.
>>
>> I wonder if we should call the release 2.0.0, and really aim only
>> WF10/EAP7 + (Open)JDK-8
>>
>> On Fri, Mar 18, 2016 at 9:31 AM, Luk?? Fry? <lukas at fryc.eu> wrote:
>>
>>> Hi guys,
>>>
>>> we are working on delivering some improvements in UPS messaging
>>> subsystem in 1.2.0,
>>>
>>> and part of that is also adoption of WF10 (with ActiveMQ Artemis
>>> underneath).
>>>
>>>
>>> The problem is that WF10 is JDK8 only, so if we use it for tests, we are
>>> limiting ourselves to JDK8-only build. We could run it on WF8 with JDK7,
>>> off course.
>>>
>>> Question is, do we want to support WF8 with UPS 1.2.0+, or should we
>>> switch to WF10 only?
>>>
>>>
>>> Cheers,
>>>
>>> ~ Lukas
>>>
>>> _______________________________________________
>>> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160318/ff6e96c1/attachment-0001.html 

From matzew at apache.org  Fri Mar 18 05:13:06 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 18 Mar 2016 10:13:06 +0100
Subject: [aerogear-dev] UPS 1.2.0+ on WF10/JDK8 - should we continue
 supporting WF8/JDK7?
In-Reply-To: <CAN+BUJpSbnQC8RSzvLsBqMju-Y=jv8+XvZJXCG-pvj4e=1Gcxg@mail.gmail.com>
References: <CAEroY35Gw8=d09XorWcyramB9xRrFuEDLK23MS-AYFEbn=RQYA@mail.gmail.com>
	<CAAg5f2QQ=u3=kaSpc2gWwm62fWYg=ZKHxDaiK8xrdkcw=LOKug@mail.gmail.com>
	<CAAg5f2Sy1mQodv1Jg=RgfrcWfMp3yWxUXMBrQZxREsX0nHnCGw@mail.gmail.com>
	<CAN+BUJpSbnQC8RSzvLsBqMju-Y=jv8+XvZJXCG-pvj4e=1Gcxg@mail.gmail.com>
Message-ID: <CAAg5f2SCtJLmXWvS_rSv2X=kTqACQBw3jDdAU0VxBcLSUWUdtw@mail.gmail.com>

On Fri, Mar 18, 2016 at 10:07 AM, Idel Pivnitskiy <idel.pivnitskiy at gmail.com
> wrote:

> +1 that release which works only with JDK-8 and WF10 should be called 2.0.0
>
> +2 that time to move to JDK-8 :) of course if we don't have special
> requirements to support JDK-7
>

for HTTP/2 and APNs, we need JDK8, I think this is the important message
here :)


>
> Best regards,
> Idel Pivnitskiy
> --
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>
> On Fri, Mar 18, 2016 at 11:41 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Another thing is, Keycloak also is now JDK-8:
>> https://github.com/keycloak/keycloak/tree/1.8.1.Final#building
>>
>> (current release is 1.9.1 and 2.0.0-CR1 is in the making)
>>
>> And one of the JDKs even called Java7 dead, sure... that's not that
>> important.
>>
>> I am very supportive of this, especially our main server platforms
>> (WildFly and EAP) are also Java8 only with the latest releases
>>
>>
>>
>> On Fri, Mar 18, 2016 at 9:34 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> For our work, required for supporting APNs' HTTP/2 APIs we also need
>>> JDK-8.
>>>
>>> I wonder if we should call the release 2.0.0, and really aim only
>>> WF10/EAP7 + (Open)JDK-8
>>>
>>> On Fri, Mar 18, 2016 at 9:31 AM, Luk?? Fry? <lukas at fryc.eu> wrote:
>>>
>>>> Hi guys,
>>>>
>>>> we are working on delivering some improvements in UPS messaging
>>>> subsystem in 1.2.0,
>>>>
>>>> and part of that is also adoption of WF10 (with ActiveMQ Artemis
>>>> underneath).
>>>>
>>>>
>>>> The problem is that WF10 is JDK8 only, so if we use it for tests, we
>>>> are limiting ourselves to JDK8-only build. We could run it on WF8 with
>>>> JDK7, off course.
>>>>
>>>> Question is, do we want to support WF8 with UPS 1.2.0+, or should we
>>>> switch to WF10 only?
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> ~ Lukas
>>>>
>>>> _______________________________________________
>>>> 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/20160318/571163f3/attachment.html 

From idel.pivnitskiy at gmail.com  Sun Mar 20 22:15:52 2016
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Mon, 21 Mar 2016 05:15:52 +0300
Subject: [aerogear-dev] [GSoC 2016] AeroGear WebPush and UnifiedPush Server
	integration
Message-ID: <CAN+BUJosKHSNb8p9tSci5WsEHw4YTw8=-fVi5_iy7zUGn9Fnww@mail.gmail.com>

Hello community!

I'm happy to work with you during the last year! Thank you for the great
project! I use it for the pleasured Open Source development when I have
free time and I use UPS with my own projects at work.

I'm highly motivated to continue my work on WebPush protocol and move it to
UPS!

Expected results for GSoC 2016 project:

   - Add WebPush support for Google Chrome, Mozilla Firefox and Safari
   browsers into UPS.
   - Integrate AeroGear WebPush server with UnifiedPush Server.
   - Good test coverage for the new code.
   - Documentation for all new developments and changes.
   - Demo application for showing the work of WebPush protocol in action
   with UPS!


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.

Glad to see your feedback!

Best regards,
Idel Pivnitskiy
--
Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160321/b3f11e4a/attachment.html 

From matzew at apache.org  Mon Mar 21 04:21:06 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 21 Mar 2016 09:21:06 +0100
Subject: [aerogear-dev] [GSoC 2016] AeroGear WebPush and UnifiedPush
 Server integration
In-Reply-To: <CAN+BUJosKHSNb8p9tSci5WsEHw4YTw8=-fVi5_iy7zUGn9Fnww@mail.gmail.com>
References: <CAN+BUJosKHSNb8p9tSci5WsEHw4YTw8=-fVi5_iy7zUGn9Fnww@mail.gmail.com>
Message-ID: <CAAg5f2QdMVvk_6+UshWv=7yD70-s2sD=WQ9CE6FqzJaYoJ1-iA@mail.gmail.com>

Hi Idel,

these ideas sound extremely awesome, and I agree they are a logic next
steps on the ground work of your project last year. The WebPush Server
needs updates too, to be compliant to latest version of the spec, right?

On Mon, Mar 21, 2016 at 3:15 AM, Idel Pivnitskiy <idel.pivnitskiy at gmail.com>
wrote:

> Hello community!
>
> I'm happy to work with you during the last year! Thank you for the great
> project! I use it for the pleasured Open Source development when I have
> free time and I use UPS with my own projects at work.
>
> I'm highly motivated to continue my work on WebPush protocol and move it
> to UPS!
>
> Expected results for GSoC 2016 project:
>
>    - Add WebPush support for Google Chrome, Mozilla Firefox and Safari
>    browsers into UPS.
>    - Integrate AeroGear WebPush server with UnifiedPush Server.
>    - Good test coverage for the new code.
>    - Documentation for all new developments and changes.
>    - Demo application for showing the work of WebPush protocol in action
>    with UPS!
>
>
> 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.
>
> Glad to see your feedback!
>
> Best regards,
> Idel Pivnitskiy
> --
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/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/20160321/34da079a/attachment.html 

From matzew at apache.org  Mon Mar 21 04:27:05 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 21 Mar 2016 09:27:05 +0100
Subject: [aerogear-dev] [GSoC 2016] AeroGear WebPush and UnifiedPush
 Server integration
In-Reply-To: <CAAg5f2QdMVvk_6+UshWv=7yD70-s2sD=WQ9CE6FqzJaYoJ1-iA@mail.gmail.com>
References: <CAN+BUJosKHSNb8p9tSci5WsEHw4YTw8=-fVi5_iy7zUGn9Fnww@mail.gmail.com>
	<CAAg5f2QdMVvk_6+UshWv=7yD70-s2sD=WQ9CE6FqzJaYoJ1-iA@mail.gmail.com>
Message-ID: <CAAg5f2T45gWhhd2YaejwHxrGY8JgDBkGkyNEZUSkpqoro2SSCg@mail.gmail.com>

a few more questions

On Mon, Mar 21, 2016 at 9:21 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi Idel,
>
> these ideas sound extremely awesome, and I agree they are a logic next
> steps on the ground work of your project last year. The WebPush Server
> needs updates too, to be compliant to latest version of the spec, right?
>
> On Mon, Mar 21, 2016 at 3:15 AM, Idel Pivnitskiy <
> idel.pivnitskiy at gmail.com> wrote:
>
>> Hello community!
>>
>> I'm happy to work with you during the last year! Thank you for the great
>> project! I use it for the pleasured Open Source development when I have
>> free time and I use UPS with my own projects at work.
>>
>> I'm highly motivated to continue my work on WebPush protocol and move it
>> to UPS!
>>
>> Expected results for GSoC 2016 project:
>>
>>    - Add WebPush support for Google Chrome, Mozilla Firefox and Safari
>>    browsers into UPS.
>>    - Integrate AeroGear WebPush server with UnifiedPush Server.
>>    - Good test coverage for the new code.
>>    - Documentation for all new developments and changes.
>>    - Demo application for showing the work of WebPush protocol in action
>>    with UPS!
>>
>> I think we could have two demos :)

- pure WebPush, via UPS, to a browser/device
- GCM push, received on WebPush APIs, going through UPS



>
>>    -
>>
>>
>> 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.
>>
>> what clients do you mean ?


>
>>    -
>>    - Port webpush-codec directly to Netty. It will simplify WebPush
>>    Server code base and attract other developers to improve the core of the
>>    protocol.
>>
>> Glad to see your feedback!
>>
>> Best regards,
>> Idel Pivnitskiy
>> --
>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>> GitHub: @idelpivnitskiy <https://github.com/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
>



-- 
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/20160321/b3ee8e09/attachment-0001.html 

From idel.pivnitskiy at gmail.com  Mon Mar 21 06:45:45 2016
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Mon, 21 Mar 2016 13:45:45 +0300
Subject: [aerogear-dev] [GSoC 2016] AeroGear WebPush and UnifiedPush
 Server integration
In-Reply-To: <CAAg5f2T45gWhhd2YaejwHxrGY8JgDBkGkyNEZUSkpqoro2SSCg@mail.gmail.com>
References: <CAN+BUJosKHSNb8p9tSci5WsEHw4YTw8=-fVi5_iy7zUGn9Fnww@mail.gmail.com>
	<CAAg5f2QdMVvk_6+UshWv=7yD70-s2sD=WQ9CE6FqzJaYoJ1-iA@mail.gmail.com>
	<CAAg5f2T45gWhhd2YaejwHxrGY8JgDBkGkyNEZUSkpqoro2SSCg@mail.gmail.com>
Message-ID: <CAN+BUJoRZnNhyg50=Mj_DGxKmS1qByc9YFpdh8NiWFd-SRUnyw@mail.gmail.com>

>
>
> On Mon, Mar 21, 2016 at 9:21 AM, Matthias Wessendorf <matzew at apache.org>
>  wrote:
>
>> Hi Idel,
>>
>> these ideas sound extremely awesome, and I agree they are a logic next
>> steps on the ground work of your project last year. The WebPush Server
>> needs updates too, to be compliant to latest version of the spec, right?
>>
>> On Mon, Mar 21, 2016 at 3:15 AM, Idel Pivnitskiy <
>> idel.pivnitskiy at gmail.com> wrote:
>>
>>> Hello community!
>>>
>>> I'm happy to work with you during the last year! Thank you for the great
>>> project! I use it for the pleasured Open Source development when I have
>>> free time and I use UPS with my own projects at work.
>>>
>>> I'm highly motivated to continue my work on WebPush protocol and move it
>>> to UPS!
>>>
>>> Expected results for GSoC 2016 project:
>>>
>>>    - Add WebPush support for Google Chrome, Mozilla Firefox and Safari
>>>    browsers into UPS.
>>>    - Integrate AeroGear WebPush server with UnifiedPush Server.
>>>    - Good test coverage for the new code.
>>>    - Documentation for all new developments and changes.
>>>    - Demo application for showing the work of WebPush protocol in
>>>    action with UPS!
>>>
>>> I think we could have two demos :)
>
> - pure WebPush, via UPS, to a browser/device
> - GCM push, received on WebPush APIs, going through UPS
>

Agree with you, demo for the usage with browsers should be developed to.


>>>    -
>>>
>>>
>>> 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.
>>>
>>> what clients do you mean ?
>

Current Java client for User Agents (
https://github.com/aerogear/aerogear-webpush-java-client), which uses Jetty
http2-client right now. And the same client for AppServer.

Best regards,
Idel Pivnitskiy
--
Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>

On Mon, Mar 21, 2016 at 11:27 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> a few more questions
>
> On Mon, Mar 21, 2016 at 9:21 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi Idel,
>>
>> these ideas sound extremely awesome, and I agree they are a logic next
>> steps on the ground work of your project last year. The WebPush Server
>> needs updates too, to be compliant to latest version of the spec, right?
>>
>> On Mon, Mar 21, 2016 at 3:15 AM, Idel Pivnitskiy <
>> idel.pivnitskiy at gmail.com> wrote:
>>
>>> Hello community!
>>>
>>> I'm happy to work with you during the last year! Thank you for the great
>>> project! I use it for the pleasured Open Source development when I have
>>> free time and I use UPS with my own projects at work.
>>>
>>> I'm highly motivated to continue my work on WebPush protocol and move it
>>> to UPS!
>>>
>>> Expected results for GSoC 2016 project:
>>>
>>>    - Add WebPush support for Google Chrome, Mozilla Firefox and Safari
>>>    browsers into UPS.
>>>    - Integrate AeroGear WebPush server with UnifiedPush Server.
>>>    - Good test coverage for the new code.
>>>    - Documentation for all new developments and changes.
>>>    - Demo application for showing the work of WebPush protocol in
>>>    action with UPS!
>>>
>>> I think we could have two demos :)
>
> - pure WebPush, via UPS, to a browser/device
> - GCM push, received on WebPush APIs, going through UPS
>
>
>
>>
>>>    -
>>>
>>>
>>> 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.
>>>
>>> what clients do you mean ?
>
>
>>
>>>    -
>>>    - Port webpush-codec directly to Netty. It will simplify WebPush
>>>    Server code base and attract other developers to improve the core of the
>>>    protocol.
>>>
>>> Glad to see your feedback!
>>>
>>> Best regards,
>>> Idel Pivnitskiy
>>> --
>>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>>> GitHub: @idelpivnitskiy <https://github.com/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
>>
>
>
>
> --
> 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/20160321/def62f30/attachment.html 

From matzew at apache.org  Mon Mar 21 06:49:18 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 21 Mar 2016 11:49:18 +0100
Subject: [aerogear-dev] [GSoC 2016] AeroGear WebPush and UnifiedPush
 Server integration
In-Reply-To: <CAN+BUJoRZnNhyg50=Mj_DGxKmS1qByc9YFpdh8NiWFd-SRUnyw@mail.gmail.com>
References: <CAN+BUJosKHSNb8p9tSci5WsEHw4YTw8=-fVi5_iy7zUGn9Fnww@mail.gmail.com>
	<CAAg5f2QdMVvk_6+UshWv=7yD70-s2sD=WQ9CE6FqzJaYoJ1-iA@mail.gmail.com>
	<CAAg5f2T45gWhhd2YaejwHxrGY8JgDBkGkyNEZUSkpqoro2SSCg@mail.gmail.com>
	<CAN+BUJoRZnNhyg50=Mj_DGxKmS1qByc9YFpdh8NiWFd-SRUnyw@mail.gmail.com>
Message-ID: <CAAg5f2Q0EDd-+KjY_aru9k6n7wQmOM=84WoWcop+skFdwHZ9Bw@mail.gmail.com>

On Mon, Mar 21, 2016 at 11:45 AM, Idel Pivnitskiy <idel.pivnitskiy at gmail.com
> wrote:

>
>> On Mon, Mar 21, 2016 at 9:21 AM, Matthias Wessendorf <matzew at apache.org>
>>  wrote:
>>
>>> Hi Idel,
>>>
>>> these ideas sound extremely awesome, and I agree they are a logic next
>>> steps on the ground work of your project last year. The WebPush Server
>>> needs updates too, to be compliant to latest version of the spec, right?
>>>
>>> On Mon, Mar 21, 2016 at 3:15 AM, Idel Pivnitskiy <
>>> idel.pivnitskiy at gmail.com> wrote:
>>>
>>>> Hello community!
>>>>
>>>> I'm happy to work with you during the last year! Thank you for the
>>>> great project! I use it for the pleasured Open Source development when I
>>>> have free time and I use UPS with my own projects at work.
>>>>
>>>> I'm highly motivated to continue my work on WebPush protocol and move
>>>> it to UPS!
>>>>
>>>> Expected results for GSoC 2016 project:
>>>>
>>>>    - Add WebPush support for Google Chrome, Mozilla Firefox and Safari
>>>>    browsers into UPS.
>>>>    - Integrate AeroGear WebPush server with UnifiedPush Server.
>>>>    - Good test coverage for the new code.
>>>>    - Documentation for all new developments and changes.
>>>>    - Demo application for showing the work of WebPush protocol in
>>>>    action with UPS!
>>>>
>>>> I think we could have two demos :)
>>
>> - pure WebPush, via UPS, to a browser/device
>> - GCM push, received on WebPush APIs, going through UPS
>>
>
> Agree with you, demo for the usage with browsers should be developed to.
>
>
>>>>    -
>>>>
>>>>
>>>> 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.
>>>>
>>>> what clients do you mean ?
>>
>
> Current Java client for User Agents (
> https://github.com/aerogear/aerogear-webpush-java-client), which uses
> Jetty http2-client right now. And the same client for AppServer.
>

ah! good point!



>
> Best regards,
> Idel Pivnitskiy
> --
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>
> On Mon, Mar 21, 2016 at 11:27 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> a few more questions
>>
>> On Mon, Mar 21, 2016 at 9:21 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi Idel,
>>>
>>> these ideas sound extremely awesome, and I agree they are a logic next
>>> steps on the ground work of your project last year. The WebPush Server
>>> needs updates too, to be compliant to latest version of the spec, right?
>>>
>>> On Mon, Mar 21, 2016 at 3:15 AM, Idel Pivnitskiy <
>>> idel.pivnitskiy at gmail.com> wrote:
>>>
>>>> Hello community!
>>>>
>>>> I'm happy to work with you during the last year! Thank you for the
>>>> great project! I use it for the pleasured Open Source development when I
>>>> have free time and I use UPS with my own projects at work.
>>>>
>>>> I'm highly motivated to continue my work on WebPush protocol and move
>>>> it to UPS!
>>>>
>>>> Expected results for GSoC 2016 project:
>>>>
>>>>    - Add WebPush support for Google Chrome, Mozilla Firefox and Safari
>>>>    browsers into UPS.
>>>>    - Integrate AeroGear WebPush server with UnifiedPush Server.
>>>>    - Good test coverage for the new code.
>>>>    - Documentation for all new developments and changes.
>>>>    - Demo application for showing the work of WebPush protocol in
>>>>    action with UPS!
>>>>
>>>> I think we could have two demos :)
>>
>> - pure WebPush, via UPS, to a browser/device
>> - GCM push, received on WebPush APIs, going through UPS
>>
>>
>>
>>>
>>>>    -
>>>>
>>>>
>>>> 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.
>>>>
>>>> what clients do you mean ?
>>
>>
>>>
>>>>    -
>>>>    - Port webpush-codec directly to Netty. It will simplify WebPush
>>>>    Server code base and attract other developers to improve the core of the
>>>>    protocol.
>>>>
>>>> Glad to see your feedback!
>>>>
>>>> Best regards,
>>>> Idel Pivnitskiy
>>>> --
>>>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>>>> GitHub: @idelpivnitskiy <https://github.com/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
>>>
>>
>>
>>
>> --
>> 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/20160321/f2be962e/attachment-0001.html 

From idel.pivnitskiy at gmail.com  Mon Mar 21 06:55:40 2016
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Mon, 21 Mar 2016 13:55:40 +0300
Subject: [aerogear-dev] [GSoC 2016] AeroGear WebPush and UnifiedPush
 Server integration
In-Reply-To: <CAAg5f2T45gWhhd2YaejwHxrGY8JgDBkGkyNEZUSkpqoro2SSCg@mail.gmail.com>
References: <CAN+BUJosKHSNb8p9tSci5WsEHw4YTw8=-fVi5_iy7zUGn9Fnww@mail.gmail.com>
	<CAAg5f2QdMVvk_6+UshWv=7yD70-s2sD=WQ9CE6FqzJaYoJ1-iA@mail.gmail.com>
	<CAAg5f2T45gWhhd2YaejwHxrGY8JgDBkGkyNEZUSkpqoro2SSCg@mail.gmail.com>
Message-ID: <CAN+BUJq3CeNX3f2wSwfkbQBXgpPU4U9Yo4TJX_hGck-U5BaNUg@mail.gmail.com>

>
> The WebPush Server needs updates too, to be compliant to latest version of
> the spec, right?


Right, but I consider it as a necessary step, which have to be done before
summer :)

Another possible scenario: complete work on integration with Chrome and
Firefox before GSoC and work on WebPush Server updates and integration with
UPS during the whole summer.

Which task has a higher priority for AeroGear?

Best regards,
Idel Pivnitskiy
--
E-mail: idel.pivnitskiy at gmail.com
Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>

On Mon, Mar 21, 2016 at 11:27 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> a few more questions
>
> On Mon, Mar 21, 2016 at 9:21 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi Idel,
>>
>> these ideas sound extremely awesome, and I agree they are a logic next
>> steps on the ground work of your project last year. The WebPush Server
>> needs updates too, to be compliant to latest version of the spec, right?
>>
>> On Mon, Mar 21, 2016 at 3:15 AM, Idel Pivnitskiy <
>> idel.pivnitskiy at gmail.com> wrote:
>>
>>> Hello community!
>>>
>>> I'm happy to work with you during the last year! Thank you for the great
>>> project! I use it for the pleasured Open Source development when I have
>>> free time and I use UPS with my own projects at work.
>>>
>>> I'm highly motivated to continue my work on WebPush protocol and move it
>>> to UPS!
>>>
>>> Expected results for GSoC 2016 project:
>>>
>>>    - Add WebPush support for Google Chrome, Mozilla Firefox and Safari
>>>    browsers into UPS.
>>>    - Integrate AeroGear WebPush server with UnifiedPush Server.
>>>    - Good test coverage for the new code.
>>>    - Documentation for all new developments and changes.
>>>    - Demo application for showing the work of WebPush protocol in
>>>    action with UPS!
>>>
>>> I think we could have two demos :)
>
> - pure WebPush, via UPS, to a browser/device
> - GCM push, received on WebPush APIs, going through UPS
>
>
>
>>
>>>    -
>>>
>>>
>>> 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.
>>>
>>> what clients do you mean ?
>
>
>>
>>>    -
>>>    - Port webpush-codec directly to Netty. It will simplify WebPush
>>>    Server code base and attract other developers to improve the core of the
>>>    protocol.
>>>
>>> Glad to see your feedback!
>>>
>>> Best regards,
>>> Idel Pivnitskiy
>>> --
>>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>>> GitHub: @idelpivnitskiy <https://github.com/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
>>
>
>
>
> --
> 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/20160321/39a569cc/attachment.html 

From idel.pivnitskiy at gmail.com  Mon Mar 21 06:59:45 2016
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Mon, 21 Mar 2016 13:59:45 +0300
Subject: [aerogear-dev] [GSoC 2016] AeroGear WebPush and UnifiedPush
 Server integration
In-Reply-To: <CAN+BUJq3CeNX3f2wSwfkbQBXgpPU4U9Yo4TJX_hGck-U5BaNUg@mail.gmail.com>
References: <CAN+BUJosKHSNb8p9tSci5WsEHw4YTw8=-fVi5_iy7zUGn9Fnww@mail.gmail.com>
	<CAAg5f2QdMVvk_6+UshWv=7yD70-s2sD=WQ9CE6FqzJaYoJ1-iA@mail.gmail.com>
	<CAAg5f2T45gWhhd2YaejwHxrGY8JgDBkGkyNEZUSkpqoro2SSCg@mail.gmail.com>
	<CAN+BUJq3CeNX3f2wSwfkbQBXgpPU4U9Yo4TJX_hGck-U5BaNUg@mail.gmail.com>
Message-ID: <CAN+BUJo+jnkJ65==mTjsCaM4Aq7PTo_8PpB1m6XXf-nJ2iMezA@mail.gmail.com>

I also want to share very interesting articles and blog posts about
WebPush, which I've found during my research of the problem:


   1.

   Web-Based Push Notifications,
   https://datatracker.ietf.org/wg/webpush/charter/
   2.

   Generic Event Delivery Using HTTP Push,
   https://tools.ietf.org/html/draft-ietf-webpush-protocol
   3.

   Message Encryption for Web Push,
   https://tools.ietf.org/html/draft-ietf-webpush-encryption
   4.

   IETF Web Push Working Group repository:
   https://github.com/webpush-wg/webpush-protocol
   5.

   Push API, https://w3c.github.io/push-api/
   6.

   Future of Push Messaging on Chrome and the Open Web,
   https://developers.google.com/web/updates/2015/03/push-notifications-on-the-open-web
   7.

   Your first push notifications web app,
   https://developers.google.com/web/fundamentals/getting-started/push-notifications/
   8.

   Web Push notifications from Irssi,
   https://hacks.mozilla.org/2015/12/web-push-notifications-from-irssi/
   9.

   Using the Push API,
   https://developer.mozilla.org/en-US/docs/Web/API/Push_API/Using_the_Push_API
   10.

   Web Push Arrives in Firefox 44,
   https://hacks.mozilla.org/2016/01/web-push-arrives-in-firefox-44/
   11.

   Mozilla Service Worker Cookbook, https://serviceworke.rs/
   12.

   Keep pushing it, with the W3C Push API,
   https://hacks.mozilla.org/2015/10/keep-pushing-it-with-the-w3c-push-api/
   13.

   Web push notifications,
   https://mobiforge.com/design-development/web-push-notifications


Some of them are really awesome :)

Best regards,
Idel Pivnitskiy
--
Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>

On Mon, Mar 21, 2016 at 1:55 PM, Idel Pivnitskiy <idel.pivnitskiy at gmail.com>
wrote:

> The WebPush Server needs updates too, to be compliant to latest version of
>> the spec, right?
>
>
> Right, but I consider it as a necessary step, which have to be done before
> summer :)
>
> Another possible scenario: complete work on integration with Chrome and
> Firefox before GSoC and work on WebPush Server updates and integration with
> UPS during the whole summer.
>
> Which task has a higher priority for AeroGear?
>
> Best regards,
> Idel Pivnitskiy
> --
> E-mail: idel.pivnitskiy at gmail.com
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>
> On Mon, Mar 21, 2016 at 11:27 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> a few more questions
>>
>> On Mon, Mar 21, 2016 at 9:21 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi Idel,
>>>
>>> these ideas sound extremely awesome, and I agree they are a logic next
>>> steps on the ground work of your project last year. The WebPush Server
>>> needs updates too, to be compliant to latest version of the spec, right?
>>>
>>> On Mon, Mar 21, 2016 at 3:15 AM, Idel Pivnitskiy <
>>> idel.pivnitskiy at gmail.com> wrote:
>>>
>>>> Hello community!
>>>>
>>>> I'm happy to work with you during the last year! Thank you for the
>>>> great project! I use it for the pleasured Open Source development when I
>>>> have free time and I use UPS with my own projects at work.
>>>>
>>>> I'm highly motivated to continue my work on WebPush protocol and move
>>>> it to UPS!
>>>>
>>>> Expected results for GSoC 2016 project:
>>>>
>>>>    - Add WebPush support for Google Chrome, Mozilla Firefox and Safari
>>>>    browsers into UPS.
>>>>    - Integrate AeroGear WebPush server with UnifiedPush Server.
>>>>    - Good test coverage for the new code.
>>>>    - Documentation for all new developments and changes.
>>>>    - Demo application for showing the work of WebPush protocol in
>>>>    action with UPS!
>>>>
>>>> I think we could have two demos :)
>>
>> - pure WebPush, via UPS, to a browser/device
>> - GCM push, received on WebPush APIs, going through UPS
>>
>>
>>
>>>
>>>>    -
>>>>
>>>>
>>>> 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.
>>>>
>>>> what clients do you mean ?
>>
>>
>>>
>>>>    -
>>>>    - Port webpush-codec directly to Netty. It will simplify WebPush
>>>>    Server code base and attract other developers to improve the core of the
>>>>    protocol.
>>>>
>>>> Glad to see your feedback!
>>>>
>>>> Best regards,
>>>> Idel Pivnitskiy
>>>> --
>>>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>>>> GitHub: @idelpivnitskiy <https://github.com/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
>>>
>>
>>
>>
>> --
>> 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/20160321/a41d7414/attachment-0001.html 

From matzew at apache.org  Mon Mar 21 07:16:19 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 21 Mar 2016 12:16:19 +0100
Subject: [aerogear-dev] [GSoC 2016] AeroGear WebPush and UnifiedPush
 Server integration
In-Reply-To: <CAN+BUJq3CeNX3f2wSwfkbQBXgpPU4U9Yo4TJX_hGck-U5BaNUg@mail.gmail.com>
References: <CAN+BUJosKHSNb8p9tSci5WsEHw4YTw8=-fVi5_iy7zUGn9Fnww@mail.gmail.com>
	<CAAg5f2QdMVvk_6+UshWv=7yD70-s2sD=WQ9CE6FqzJaYoJ1-iA@mail.gmail.com>
	<CAAg5f2T45gWhhd2YaejwHxrGY8JgDBkGkyNEZUSkpqoro2SSCg@mail.gmail.com>
	<CAN+BUJq3CeNX3f2wSwfkbQBXgpPU4U9Yo4TJX_hGck-U5BaNUg@mail.gmail.com>
Message-ID: <CAAg5f2Ryv1QDHMwhjbMuK37ZB7SJPLan=jFcjOO1wNLchXZfLA@mail.gmail.com>

On Mon, Mar 21, 2016 at 11:55 AM, Idel Pivnitskiy <idel.pivnitskiy at gmail.com
> wrote:

> The WebPush Server needs updates too, to be compliant to latest version of
>> the spec, right?
>
>
> Right, but I consider it as a necessary step, which have to be done before
> summer :)
>
> Another possible scenario: complete work on integration with Chrome and
> Firefox before GSoC
>

work like that is always more than welcome - and would be handy to actually
show the 'standalone' solution: pure WebPush -> FF/Chrome (without UPS).
I think we could a screencast on this one, once done

-M


> and work on WebPush Server updates and integration with UPS during the
> whole summer.
>
> Which task has a higher priority for AeroGear?
>
> Best regards,
> Idel Pivnitskiy
> --
> E-mail: idel.pivnitskiy at gmail.com
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>
> On Mon, Mar 21, 2016 at 11:27 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> a few more questions
>>
>> On Mon, Mar 21, 2016 at 9:21 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi Idel,
>>>
>>> these ideas sound extremely awesome, and I agree they are a logic next
>>> steps on the ground work of your project last year. The WebPush Server
>>> needs updates too, to be compliant to latest version of the spec, right?
>>>
>>> On Mon, Mar 21, 2016 at 3:15 AM, Idel Pivnitskiy <
>>> idel.pivnitskiy at gmail.com> wrote:
>>>
>>>> Hello community!
>>>>
>>>> I'm happy to work with you during the last year! Thank you for the
>>>> great project! I use it for the pleasured Open Source development when I
>>>> have free time and I use UPS with my own projects at work.
>>>>
>>>> I'm highly motivated to continue my work on WebPush protocol and move
>>>> it to UPS!
>>>>
>>>> Expected results for GSoC 2016 project:
>>>>
>>>>    - Add WebPush support for Google Chrome, Mozilla Firefox and Safari
>>>>    browsers into UPS.
>>>>    - Integrate AeroGear WebPush server with UnifiedPush Server.
>>>>    - Good test coverage for the new code.
>>>>    - Documentation for all new developments and changes.
>>>>    - Demo application for showing the work of WebPush protocol in
>>>>    action with UPS!
>>>>
>>>> I think we could have two demos :)
>>
>> - pure WebPush, via UPS, to a browser/device
>> - GCM push, received on WebPush APIs, going through UPS
>>
>>
>>
>>>
>>>>    -
>>>>
>>>>
>>>> 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.
>>>>
>>>> what clients do you mean ?
>>
>>
>>>
>>>>    -
>>>>    - Port webpush-codec directly to Netty. It will simplify WebPush
>>>>    Server code base and attract other developers to improve the core of the
>>>>    protocol.
>>>>
>>>> Glad to see your feedback!
>>>>
>>>> Best regards,
>>>> Idel Pivnitskiy
>>>> --
>>>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>>>> GitHub: @idelpivnitskiy <https://github.com/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
>>>
>>
>>
>>
>> --
>> 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/20160321/99706c5d/attachment.html 

From matzew at apache.org  Mon Mar 21 10:25:08 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 21 Mar 2016 15:25:08 +0100
Subject: [aerogear-dev] AG Parent 0.2.20 - staging repository
Message-ID: <CAAg5f2RPUkis-afMP5ec_wCeCgR5XoFCUAbJKfitt1bJfUR0eQ@mail.gmail.com>

Ahoy!

A new release of aerogear-parent was staged at:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7897/

This is basically an update of the GCM JAR we use in UPS. Now there is an
offical artifact from Google on maven central - already having GCM-3 support

BTW. I'm considering to release it tomorrow. If you want
the release to be postponed to another day, let me know.

-- 
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/20160321/dc39f53c/attachment.html 

From supittma at redhat.com  Mon Mar 21 10:26:27 2016
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 21 Mar 2016 10:26:27 -0400
Subject: [aerogear-dev] AG Parent 0.2.20 - staging repository
In-Reply-To: <CAAg5f2RPUkis-afMP5ec_wCeCgR5XoFCUAbJKfitt1bJfUR0eQ@mail.gmail.com>
References: <CAAg5f2RPUkis-afMP5ec_wCeCgR5XoFCUAbJKfitt1bJfUR0eQ@mail.gmail.com>
Message-ID: <CAEQz2CuemU8_3uPPwp4Nh71GPvtfwApJv7QVVSCXWLcbbyHajA@mail.gmail.com>

+1

On Mon, Mar 21, 2016 at 10:25 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Ahoy!
>
> A new release of aerogear-parent was staged at:
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7897/
>
> This is basically an update of the GCM JAR we use in UPS. Now there is an
> offical artifact from Google on maven central - already having GCM-3 support
>
> BTW. I'm considering to release it tomorrow. If you want
> the release to be postponed to another day, let me know.
>
> --
> 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/20160321/5edae751/attachment.html 

From avibelli at redhat.com  Mon Mar 21 10:55:50 2016
From: avibelli at redhat.com (Andrea Vibelli)
Date: Mon, 21 Mar 2016 07:55:50 -0700 (MST)
Subject: [aerogear-dev] AG Parent 0.2.20 - staging repository
In-Reply-To: <CAAg5f2RPUkis-afMP5ec_wCeCgR5XoFCUAbJKfitt1bJfUR0eQ@mail.gmail.com>
References: <CAAg5f2RPUkis-afMP5ec_wCeCgR5XoFCUAbJKfitt1bJfUR0eQ@mail.gmail.com>
Message-ID: <1458572150480-12420.post@n5.nabble.com>

Looks good Matt, thanks!

Andrea

Matthias Wessendorf wrote
> Ahoy!
> 
> A new release of aerogear-parent was staged at:
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7897/
> 
> This is basically an update of the GCM JAR we use in UPS. Now there is an
> offical artifact from Google on maven central - already having GCM-3
> support
> 
> BTW. I'm considering to release it tomorrow. If you want
> the release to be postponed to another day, let me know.
> 
> -- 
> 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 .jboss

> https://lists.jboss.org/mailman/listinfo/aerogear-dev





--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AG-Parent-0-2-20-staging-repository-tp12418p12420.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From kpiwko at redhat.com  Mon Mar 21 12:33:22 2016
From: kpiwko at redhat.com (Karel Piwko)
Date: Mon, 21 Mar 2016 17:33:22 +0100
Subject: [aerogear-dev] AG Parent 0.2.20 - staging repository
In-Reply-To: <1458572150480-12420.post@n5.nabble.com>
References: <CAAg5f2RPUkis-afMP5ec_wCeCgR5XoFCUAbJKfitt1bJfUR0eQ@mail.gmail.com>
	<1458572150480-12420.post@n5.nabble.com>
Message-ID: <CAPXQee4bU3borMe_1vJbzoscZwd==cXeDvOkG-gLhcar9H6+4w@mail.gmail.com>

Look good to me!

Side note, funny that we go version backwards due to groupId change but I
hope that Google will maintain the library and will keep adding new
functionality - such as QE long standing
https://github.com/google/gcm/issues/165

Cheers,

Karel

On Mon, Mar 21, 2016 at 3:55 PM, Andrea Vibelli <avibelli at redhat.com> wrote:

> Looks good Matt, thanks!
>
> Andrea
>
> Matthias Wessendorf wrote
> > Ahoy!
> >
> > A new release of aerogear-parent was staged at:
> >
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7897/
> >
> > This is basically an update of the GCM JAR we use in UPS. Now there is an
> > offical artifact from Google on maven central - already having GCM-3
> > support
> >
> > BTW. I'm considering to release it tomorrow. If you want
> > the release to be postponed to another day, let me know.
> >
> > --
> > 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 .jboss
>
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
>
> --
> View this message in context:
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AG-Parent-0-2-20-staging-repository-tp12418p12420.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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160321/997dd756/attachment.html 

From matzew at apache.org  Mon Mar 21 12:40:17 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 21 Mar 2016 17:40:17 +0100
Subject: [aerogear-dev] AG Parent 0.2.20 - staging repository
In-Reply-To: <CAPXQee4bU3borMe_1vJbzoscZwd==cXeDvOkG-gLhcar9H6+4w@mail.gmail.com>
References: <CAAg5f2RPUkis-afMP5ec_wCeCgR5XoFCUAbJKfitt1bJfUR0eQ@mail.gmail.com>
	<1458572150480-12420.post@n5.nabble.com>
	<CAPXQee4bU3borMe_1vJbzoscZwd==cXeDvOkG-gLhcar9H6+4w@mail.gmail.com>
Message-ID: <CAAg5f2TYdtMZgdpueJSSVpew6vyDHyUq47sj6M4qVEi8QNxfCg@mail.gmail.com>

On Mon, Mar 21, 2016 at 5:33 PM, Karel Piwko <kpiwko at redhat.com> wrote:

> Look good to me!
>
> Side note, funny that we go version backwards due to groupId change
>

I think the version means nothing.

Google drops their newer with 1.0.0 - tjey never had anything out there,
hence a 1.0.0 makes sense


> but I hope that Google will maintain the library and will keep adding new
> functionality - such as QE long standing
> https://github.com/google/gcm/issues/165
>

yeah saw that, and was smiling :)


>
> Cheers,
>
> Karel
>
> On Mon, Mar 21, 2016 at 3:55 PM, Andrea Vibelli <avibelli at redhat.com>
> wrote:
>
>> Looks good Matt, thanks!
>>
>> Andrea
>>
>> Matthias Wessendorf wrote
>> > Ahoy!
>> >
>> > A new release of aerogear-parent was staged at:
>> >
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7897/
>> >
>> > This is basically an update of the GCM JAR we use in UPS. Now there is
>> an
>> > offical artifact from Google on maven central - already having GCM-3
>> > support
>> >
>> > BTW. I'm considering to release it tomorrow. If you want
>> > the release to be postponed to another day, let me know.
>> >
>> > --
>> > 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 .jboss
>>
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AG-Parent-0-2-20-staging-repository-tp12418p12420.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
>>
>
>
> _______________________________________________
> 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/20160321/34dc5ff4/attachment.html 

From matzew at apache.org  Mon Mar 21 12:40:30 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 21 Mar 2016 17:40:30 +0100
Subject: [aerogear-dev] AG Parent 0.2.20 - staging repository
In-Reply-To: <CAAg5f2TYdtMZgdpueJSSVpew6vyDHyUq47sj6M4qVEi8QNxfCg@mail.gmail.com>
References: <CAAg5f2RPUkis-afMP5ec_wCeCgR5XoFCUAbJKfitt1bJfUR0eQ@mail.gmail.com>
	<1458572150480-12420.post@n5.nabble.com>
	<CAPXQee4bU3borMe_1vJbzoscZwd==cXeDvOkG-gLhcar9H6+4w@mail.gmail.com>
	<CAAg5f2TYdtMZgdpueJSSVpew6vyDHyUq47sj6M4qVEi8QNxfCg@mail.gmail.com>
Message-ID: <CAAg5f2R1A9+CeZrFiceC1r3zVtHX+7iLPFnkN532GJVd1=Jx-A@mail.gmail.com>

Ok, I will release the kracken !

On Mon, Mar 21, 2016 at 5:40 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Mon, Mar 21, 2016 at 5:33 PM, Karel Piwko <kpiwko at redhat.com> wrote:
>
>> Look good to me!
>>
>> Side note, funny that we go version backwards due to groupId change
>>
>
> I think the version means nothing.
>
> Google drops their newer with 1.0.0 - tjey never had anything out there,
> hence a 1.0.0 makes sense
>
>
>> but I hope that Google will maintain the library and will keep adding new
>> functionality - such as QE long standing
>> https://github.com/google/gcm/issues/165
>>
>
> yeah saw that, and was smiling :)
>
>
>>
>> Cheers,
>>
>> Karel
>>
>> On Mon, Mar 21, 2016 at 3:55 PM, Andrea Vibelli <avibelli at redhat.com>
>> wrote:
>>
>>> Looks good Matt, thanks!
>>>
>>> Andrea
>>>
>>> Matthias Wessendorf wrote
>>> > Ahoy!
>>> >
>>> > A new release of aerogear-parent was staged at:
>>> >
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7897/
>>> >
>>> > This is basically an update of the GCM JAR we use in UPS. Now there is
>>> an
>>> > offical artifact from Google on maven central - already having GCM-3
>>> > support
>>> >
>>> > BTW. I'm considering to release it tomorrow. If you want
>>> > the release to be postponed to another day, let me know.
>>> >
>>> > --
>>> > 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 .jboss
>>>
>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AG-Parent-0-2-20-staging-repository-tp12418p12420.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
>>>
>>
>>
>> _______________________________________________
>> 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/20160321/9739abc3/attachment.html 

From matzew at apache.org  Tue Mar 22 09:20:51 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 22 Mar 2016 14:20:51 +0100
Subject: [aerogear-dev] AeroGear Push PHP Package
Message-ID: <CAAg5f2RTDyR3tk-TWOgWNDT41MrX_P4rZ8=8DdrK+NndrF92UQ@mail.gmail.com>

Hi,

a member of the AeroGear community now wrote a PHP library:
https://github.com/Napp/AeroGear-Push

-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/20160322/abb1ec48/attachment-0001.html 

From matzew at apache.org  Tue Mar 22 11:13:44 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 22 Mar 2016 16:13:44 +0100
Subject: [aerogear-dev] onMessage() invoked in a loop?
Message-ID: <CAAg5f2QNkQ2p-tBd8xaJ4hhL3xRTDrV1hcLQzTiwAt_FJvFnuw@mail.gmail.com>

Hi,

I noticed this is invoked in a loop (every second):
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/jms/TriggerMetricCollectionConsumer.java#L54

any ideas?

-- 
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/20160322/f9cb552a/attachment.html 

From lfryc at redhat.com  Tue Mar 22 15:59:56 2016
From: lfryc at redhat.com (Lukas Fryc)
Date: Tue, 22 Mar 2016 20:59:56 +0100
Subject: [aerogear-dev] onMessage() invoked in a loop?
In-Reply-To: <CAAg5f2QNkQ2p-tBd8xaJ4hhL3xRTDrV1hcLQzTiwAt_FJvFnuw@mail.gmail.com>
References: <CAAg5f2QNkQ2p-tBd8xaJ4hhL3xRTDrV1hcLQzTiwAt_FJvFnuw@mail.gmail.com>
Message-ID: <CAAnALH=tAdCEF3QuchtZgwhQxYOKuQxEN6B-9OkmmFBc0yU9PQ@mail.gmail.com>

Hey Matthias,

that is by design - until MetricCollector detects that all tokens were
loaded && all metrics were processed, it rolls back the event from the
TriggerMetricCollectionQueue.

It means that it is triggered "in loop" until push message processing
completely finishes.

But, if it never finishes completely, you are hitting a bug.


Cheers,

~ Lukas

On Tue, Mar 22, 2016 at 4:13 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> I noticed this is invoked in a loop (every second):
>
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/jms/TriggerMetricCollectionConsumer.java#L54
>
> any ideas?
>
> --
> 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
>



-- 
Luk?? Fry?
Software Engineer
Red Hat Mobile | AeroGear.org, FeedHenry.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160322/6657b622/attachment.html 

From matzew at apache.org  Tue Mar 22 16:09:48 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 22 Mar 2016 21:09:48 +0100
Subject: [aerogear-dev] onMessage() invoked in a loop?
In-Reply-To: <CAAnALH=tAdCEF3QuchtZgwhQxYOKuQxEN6B-9OkmmFBc0yU9PQ@mail.gmail.com>
References: <CAAg5f2QNkQ2p-tBd8xaJ4hhL3xRTDrV1hcLQzTiwAt_FJvFnuw@mail.gmail.com>
	<CAAnALH=tAdCEF3QuchtZgwhQxYOKuQxEN6B-9OkmmFBc0yU9PQ@mail.gmail.com>
Message-ID: <CAAg5f2SRuh0e5G6irSvvn5xTJmxN=2miV6SQ3crawEkeRyc2wA@mail.gmail.com>

On Tue, Mar 22, 2016 at 8:59 PM, Lukas Fryc <lfryc at redhat.com> wrote:

> Hey Matthias,
>
> that is by design - until MetricCollector detects that all tokens were
> loaded && all metrics were processed, it rolls back the event from the
> TriggerMetricCollectionQueue.
>
> It means that it is triggered "in loop" until push message processing
> completely finishes.
>
> But, if it never finishes completely, you are hitting a bug.
>

yeah, I was expecting it's in a loop for a reason - but that loop never
ends. It stays even after a number of Wildfly reboots. That's what made we
wonder :)




>
>
> Cheers,
>
> ~ Lukas
>
> On Tue, Mar 22, 2016 at 4:13 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> I noticed this is invoked in a loop (every second):
>>
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/jms/TriggerMetricCollectionConsumer.java#L54
>>
>> any ideas?
>>
>> --
>> 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
>>
>
>
>
> --
> Luk?? Fry?
> Software Engineer
> Red Hat Mobile | AeroGear.org, FeedHenry.org
>
> _______________________________________________
> 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/20160322/f79be9e2/attachment.html 

From matzew at apache.org  Wed Mar 23 14:58:54 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 23 Mar 2016 19:58:54 +0100
Subject: [aerogear-dev] Staging of UnifiedPush Server 1.1.2
Message-ID: <CAAg5f2Tsop1DsmZsOKuPkSYtnG7PSdzZXKspCOEcL2sghxAg6g@mail.gmail.com>

Hello there!

almost three weeks after our 1.1.1.Final release, there is a new version
(1.1.2.Final) on the horizon.

You can find the staging repository here:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7909/

The version contains a few fixes and minor improvements. A full list of all
changes is listed here:
https://issues.jboss.org/projects/AGPUSH/versions/12329895

Please give it a try over the next few days, so that we can release it
early next week!

Happy Easter ? !

-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/20160323/04169900/attachment.html 

From matzew at apache.org  Wed Mar 23 17:57:48 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 23 Mar 2016 22:57:48 +0100
Subject: [aerogear-dev] UPS Wizard - UI bug
Message-ID: <CAAg5f2TsS5Rvtv+iUuBWSwSCRpLNRJefifbd_8FQCMXpXvXMDQ@mail.gmail.com>

Hi,

building master, and deploying to a fresh (I did unzip it and also ran the
two CLI script right before the deployment) WildFly-10, I am getting a bug
on the Wizard:

* After adding the variant, the code snippets are lacking. See here:
https://www.dropbox.com/s/8x8cptap3h5yidu/Screen%20Shot%202016-03-23%20at%2022.49.27.png?dl=0


In the console, I am getting a weird JS error:

modules.cb6244c0.js:6 TypeError: Cannot read property 'forEach' of undefined
    at Object.generate (scripts.d0f6b7bb.js:2)
    at renderSnippets (scripts.d0f6b7bb.js:2)
    at new controller (scripts.d0f6b7bb.js:2)
    at Object.invoke (modules.cb6244c0.js:4)
    at extend.instance (modules.cb6244c0.js:5)
    at nodeLinkFn (modules.cb6244c0.js:5)
    at modules.cb6244c0.js:5
    at processQueue (modules.cb6244c0.js:7)
    at modules.cb6244c0.js:7
    at Scope.$eval (modules.cb6244c0.js:7)(anonymous function) @
modules.cb6244c0.js:6
modules.cb6244c0.js:6 Notification was successfully sent
modules.cb6244c0.js:6 Application Ad successfully created
modules.cb6244c0.js:6 Variant dasdadas successfully created
modules.cb6244c0.js:6 TypeError: Cannot read property 'forEach' of undefined
    at Object.generate (scripts.d0f6b7bb.js:2)
    at renderSnippets (scripts.d0f6b7bb.js:2)
    at new controller (scripts.d0f6b7bb.js:2)
    at Object.invoke (modules.cb6244c0.js:4)
    at extend.instance (modules.cb6244c0.js:5)
    at nodeLinkFn (modules.cb6244c0.js:5)
    at modules.cb6244c0.js:5
    at processQueue (modules.cb6244c0.js:7)
    at modules.cb6244c0.js:7
    at Scope.$eval (modules.cb6244c0.js:7)

I wonder if something went wrong, when building the UI ?

-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/20160323/8f99f7fb/attachment-0001.html 

From matzew at apache.org  Wed Mar 23 19:42:46 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 24 Mar 2016 00:42:46 +0100
Subject: [aerogear-dev] Artemis bug on WildFly-10
Message-ID: <CAAg5f2QOJQ6e_c4aUtTFqcrtp6XwQ65TzbZqQ=jc=G2+VF5Gww@mail.gmail.com>

Hi,

more as a FYI....

I am in the process of updating our Docker -DEV image to WF/10 (see [1]),
and I noticed a bug in Artemis:


Caused by: javax.jms.JMSException: Failed to create session factory
at
org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:727)
at
org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:233)
at
org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:229)
at
org.jboss.aerogear.unifiedpush.message.util.JmsClient$JmsReceiver.from(JmsClient.java:173)
... 172 more
Caused by:
ActiveMQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT
message=AMQ119013: Timed out waiting to receive cluster topology.
Group:null]
at
org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:813)
at
org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:724)
... 175 more
Now, this issue is addressed by
https://issues.apache.org/jira/browse/ARTEMIS-385 and fixed in
ActiveMQ-Artemis 1.3.0 (unreleased), but WildFly 10.x is (currently) on
their 1.1.0 version.

Worth to mention; I think I am unable to reproduce this directly on my Mac,
just w/ CentOS7 and WF-10 (via ), using this image:
https://github.com/jboss-dockerfiles/wildfly/tree/10.0.0.Final


Cheers,
Matthias

[1] https://github.com/matzew/dockerfiles/tree/WF_10_ups_120


-- 
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/20160324/b28095ce/attachment.html 

From heldner at glue.ch  Thu Mar 17 09:44:30 2016
From: heldner at glue.ch (cel)
Date: Thu, 17 Mar 2016 06:44:30 -0700 (MST)
Subject: [aerogear-dev] GCM Device Token not accepted
Message-ID: <1458222270230-12403.post@n5.nabble.com>

The new device Token returned by the new GCM - API for Android (using
InstanceId.getToken  instead of gcm.register(context), which is deprecated)
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
push notifications from aerogear can be sent to that device. Is this a Bug?
Has this been fixed in newer versions? 




--
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.

From matzew at apache.org  Wed Mar 23 20:00:49 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 24 Mar 2016 01:00:49 +0100
Subject: [aerogear-dev] GCM Device Token not accepted
In-Reply-To: <1458222270230-12403.post@n5.nabble.com>
References: <1458222270230-12403.post@n5.nabble.com>
Message-ID: <CAAg5f2R0TjM-6TSkkmqhj4ngG+V70XBiRQf_XEd3MtSj9gF4nA@mail.gmail.com>

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 <heldner at glue.ch> 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
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160324/6c1c3f4d/attachment.html 

From matzew at apache.org  Wed Mar 23 20:34:17 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 24 Mar 2016 01:34:17 +0100
Subject: [aerogear-dev] GCM Device Token not accepted
In-Reply-To: <CAAg5f2R0TjM-6TSkkmqhj4ngG+V70XBiRQf_XEd3MtSj9gF4nA@mail.gmail.com>
References: <1458222270230-12403.post@n5.nabble.com>
	<CAAg5f2R0TjM-6TSkkmqhj4ngG+V70XBiRQf_XEd3MtSj9gF4nA@mail.gmail.com>
Message-ID: <CAAg5f2QzCnbghitXV9O7O0WAYBc6L6=iNRN-ygZPjuB6bezpTQ@mail.gmail.com>

On Thu, Mar 24, 2016 at 1:00 AM, Matthias Wessendorf <matzew at apache.org>
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 <heldner at glue.ch> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160324/7e2a3eca/attachment-0001.html 

From lfryc at redhat.com  Thu Mar 24 03:26:19 2016
From: lfryc at redhat.com (Lukas Fryc)
Date: Thu, 24 Mar 2016 08:26:19 +0100
Subject: [aerogear-dev] UPS Wizard - UI bug
In-Reply-To: <CAAg5f2TsS5Rvtv+iUuBWSwSCRpLNRJefifbd_8FQCMXpXvXMDQ@mail.gmail.com>
References: <CAAg5f2TsS5Rvtv+iUuBWSwSCRpLNRJefifbd_8FQCMXpXvXMDQ@mail.gmail.com>
Message-ID: <CAAnALHn-APOMcWKTAg_W6e5a5bTtg24vspvPvuCQ-1Q-4sBMPw@mail.gmail.com>

Hey Matthias,

I believe this PR actually fixes it:
https://github.com/aerogear/aerogear-unifiedpush-server/pull/700

I noticed it yesterday when doing autofocus work as well, see a second
commit there.

~ L.

On Wed, Mar 23, 2016 at 10:57 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> building master, and deploying to a fresh (I did unzip it and also ran the
> two CLI script right before the deployment) WildFly-10, I am getting a bug
> on the Wizard:
>
> * After adding the variant, the code snippets are lacking. See here:
>
> https://www.dropbox.com/s/8x8cptap3h5yidu/Screen%20Shot%202016-03-23%20at%2022.49.27.png?dl=0
>
>
> In the console, I am getting a weird JS error:
>
> modules.cb6244c0.js:6 TypeError: Cannot read property 'forEach' of
> undefined
>     at Object.generate (scripts.d0f6b7bb.js:2)
>     at renderSnippets (scripts.d0f6b7bb.js:2)
>     at new controller (scripts.d0f6b7bb.js:2)
>     at Object.invoke (modules.cb6244c0.js:4)
>     at extend.instance (modules.cb6244c0.js:5)
>     at nodeLinkFn (modules.cb6244c0.js:5)
>     at modules.cb6244c0.js:5
>     at processQueue (modules.cb6244c0.js:7)
>     at modules.cb6244c0.js:7
>     at Scope.$eval (modules.cb6244c0.js:7)(anonymous function) @
> modules.cb6244c0.js:6
> modules.cb6244c0.js:6 Notification was successfully sent
> modules.cb6244c0.js:6 Application Ad successfully created
> modules.cb6244c0.js:6 Variant dasdadas successfully created
> modules.cb6244c0.js:6 TypeError: Cannot read property 'forEach' of
> undefined
>     at Object.generate (scripts.d0f6b7bb.js:2)
>     at renderSnippets (scripts.d0f6b7bb.js:2)
>     at new controller (scripts.d0f6b7bb.js:2)
>     at Object.invoke (modules.cb6244c0.js:4)
>     at extend.instance (modules.cb6244c0.js:5)
>     at nodeLinkFn (modules.cb6244c0.js:5)
>     at modules.cb6244c0.js:5
>     at processQueue (modules.cb6244c0.js:7)
>     at modules.cb6244c0.js:7
>     at Scope.$eval (modules.cb6244c0.js:7)
>
> I wonder if something went wrong, when building the UI ?
>
> -Matthias
>
> --
> 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
>



-- 
Luk?? Fry?
Software Engineer
Red Hat Mobile | AeroGear.org, FeedHenry.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160324/ebb971c4/attachment.html 

From matzew at apache.org  Thu Mar 24 04:39:40 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 24 Mar 2016 09:39:40 +0100
Subject: [aerogear-dev] Staging of UnifiedPush Server 1.1.2
In-Reply-To: <CAAg5f2Tsop1DsmZsOKuPkSYtnG7PSdzZXKspCOEcL2sghxAg6g@mail.gmail.com>
References: <CAAg5f2Tsop1DsmZsOKuPkSYtnG7PSdzZXKspCOEcL2sghxAg6g@mail.gmail.com>
Message-ID: <CAAg5f2SFLOEvEhmGtk_YqW0aR6FmwyYnbUd+gyjApqaMEU_=+g@mail.gmail.com>

I will restage a new version in a bit.

the UI bug, fixed
https://github.com/aerogear/aerogear-unifiedpush-server/pull/700, is also
on 1.1.2

-M

On Wed, Mar 23, 2016 at 7:58 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hello there!
>
> almost three weeks after our 1.1.1.Final release, there is a new version
> (1.1.2.Final) on the horizon.
>
> You can find the staging repository here:
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7909/
>
> The version contains a few fixes and minor improvements. A full list of
> all changes is listed here:
> https://issues.jboss.org/projects/AGPUSH/versions/12329895
>
> Please give it a try over the next few days, so that we can release it
> early next week!
>
> Happy Easter ? !
>
> -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/20160324/dd120088/attachment.html 

From matzew at apache.org  Thu Mar 24 05:41:09 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 24 Mar 2016 10:41:09 +0100
Subject: [aerogear-dev] Staging of UnifiedPush Server 1.1.2
In-Reply-To: <CAAg5f2SFLOEvEhmGtk_YqW0aR6FmwyYnbUd+gyjApqaMEU_=+g@mail.gmail.com>
References: <CAAg5f2Tsop1DsmZsOKuPkSYtnG7PSdzZXKspCOEcL2sghxAg6g@mail.gmail.com>
	<CAAg5f2SFLOEvEhmGtk_YqW0aR6FmwyYnbUd+gyjApqaMEU_=+g@mail.gmail.com>
Message-ID: <CAAg5f2Qjz4V+jB0sym6rq5jS=nBgEzPCuXfViJ52KkB=FEcsOA@mail.gmail.com>

here we go:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7915/

On Thu, Mar 24, 2016 at 9:39 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> I will restage a new version in a bit.
>
> the UI bug, fixed
> https://github.com/aerogear/aerogear-unifiedpush-server/pull/700, is also
> on 1.1.2
>
> -M
>
> On Wed, Mar 23, 2016 at 7:58 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hello there!
>>
>> almost three weeks after our 1.1.1.Final release, there is a new version
>> (1.1.2.Final) on the horizon.
>>
>> You can find the staging repository here:
>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7909/
>>
>> The version contains a few fixes and minor improvements. A full list of
>> all changes is listed here:
>> https://issues.jboss.org/projects/AGPUSH/versions/12329895
>>
>> Please give it a try over the next few days, so that we can release it
>> early next week!
>>
>> Happy Easter ? !
>>
>> -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/20160324/e7187d5a/attachment.html 

From matzew at apache.org  Tue Mar 29 00:14:52 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 29 Mar 2016 06:14:52 +0200
Subject: [aerogear-dev] Shipping! (was: Re: Staging of UnifiedPush Server
	1.1.2)
Message-ID: <CAAg5f2Qodmeogib8qY6rBhudn4Cz2ToJOBg9vFesReLxtUq8FA@mail.gmail.com>

Just klicked the button, and artifacts will be uploaded to maven central.

JIRA and GH, updated:
https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.1.2.Final

Enjoy!

-Matthias


On Thu, Mar 24, 2016 at 10:41 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> here we go:
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7915/
>
> On Thu, Mar 24, 2016 at 9:39 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> I will restage a new version in a bit.
>>
>> the UI bug, fixed
>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/700, is
>> also on 1.1.2
>>
>> -M
>>
>> On Wed, Mar 23, 2016 at 7:58 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hello there!
>>>
>>> almost three weeks after our 1.1.1.Final release, there is a new version
>>> (1.1.2.Final) on the horizon.
>>>
>>> You can find the staging repository here:
>>>
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7909/
>>>
>>> The version contains a few fixes and minor improvements. A full list of
>>> all changes is listed here:
>>> https://issues.jboss.org/projects/AGPUSH/versions/12329895
>>>
>>> Please give it a try over the next few days, so that we can release it
>>> early next week!
>>>
>>> Happy Easter ? !
>>>
>>> -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
>



-- 
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/20160329/fd2b09ca/attachment-0001.html 

From supittma at redhat.com  Wed Mar 30 11:14:13 2016
From: supittma at redhat.com (Summers Pittman)
Date: Wed, 30 Mar 2016 11:14:13 -0400
Subject: [aerogear-dev] GCM Device Token not accepted
In-Reply-To: <CAAg5f2QzCnbghitXV9O7O0WAYBc6L6=iNRN-ygZPjuB6bezpTQ@mail.gmail.com>
References: <1458222270230-12403.post@n5.nabble.com>
	<CAAg5f2R0TjM-6TSkkmqhj4ngG+V70XBiRQf_XEd3MtSj9gF4nA@mail.gmail.com>
	<CAAg5f2QzCnbghitXV9O7O0WAYBc6L6=iNRN-ygZPjuB6bezpTQ@mail.gmail.com>
Message-ID: <CAEQz2Cv7hCfWjqn2GukNMWEd_wz22N-g22t598ymJMUTkqrE_Q@mail.gmail.com>

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 <matzew at apache.org>
wrote:

>
>
> On Thu, Mar 24, 2016 at 1:00 AM, Matthias Wessendorf <matzew at apache.org>
> 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 <heldner at glue.ch> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160330/3acc96fc/attachment.html 

From matzew at apache.org  Wed Mar 30 22:04:44 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 31 Mar 2016 04:04:44 +0200
Subject: [aerogear-dev] GCM patch to 'older' 0.2.17 parent
Message-ID: <CAAg5f2SFzJixuCPKhwb=BSGVrxNF4H01zbT=hKucBJ3UrrcZWg@mail.gmail.com>

Hi,

on our 1.1.x branch, we use 0.2.17 of parent: good

Due to some reasons (e.g. much higher Keycloak version) we can not use
0.2.20, but I'd like to use Google's GCM drop on 1..1x as well for a few
reasons:

* better updates and patches (from Google)
* back port of the GCM prio patch from Summers to 1.1.x

Here is the staging repo:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7948/

I'd like to release on Friday, if there no concerns...

-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/20160331/be17d492/attachment.html 

From supittma at redhat.com  Thu Mar 31 08:40:52 2016
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 31 Mar 2016 08:40:52 -0400
Subject: [aerogear-dev] GCM patch to 'older' 0.2.17 parent
In-Reply-To: <CAAg5f2SFzJixuCPKhwb=BSGVrxNF4H01zbT=hKucBJ3UrrcZWg@mail.gmail.com>
References: <CAAg5f2SFzJixuCPKhwb=BSGVrxNF4H01zbT=hKucBJ3UrrcZWg@mail.gmail.com>
Message-ID: <CAEQz2Ct0B=FXdnw5kgWRdWX4P9jq02Fed8d9YAmMo9Kki6bG1w@mail.gmail.com>

None on my end.

On Wed, Mar 30, 2016 at 10:04 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> on our 1.1.x branch, we use 0.2.17 of parent: good
>
> Due to some reasons (e.g. much higher Keycloak version) we can not use
> 0.2.20, but I'd like to use Google's GCM drop on 1..1x as well for a few
> reasons:
>
> * better updates and patches (from Google)
> * back port of the GCM prio patch from Summers to 1.1.x
>
> Here is the staging repo:
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7948/
>
> I'd like to release on Friday, if there no concerns...
>
> -Matthias
>
> --
> 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/20160331/a1bf01dc/attachment.html