From matzew at apache.org  Mon May  2 03:16:36 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 2 May 2016 09:16:36 +0200
Subject: [aerogear-dev] Google Service Gradle Plugin
In-Reply-To: <CAEQz2CtsOxGs9zvoBhG1yCnpUuKksOEBqdz6SG3Cnx5R-u77xA@mail.gmail.com>
References: <CAEQz2CsSZRhsJqzoOaMCVuRDfmEhB22UjhHBrVDrF7gSiAN_2g@mail.gmail.com>
	<CAAg5f2RCdj-bUbLDT_e9z19A7O9Bc=gG0RBccetUUm3ja6kn0w@mail.gmail.com>
	<CAAg5f2SkYECgcJ5i6fqTjfA+2pGxmfbxg7ZQzi1ofmsRjzHixQ@mail.gmail.com>
	<CAEQz2CtsOxGs9zvoBhG1yCnpUuKksOEBqdz6SG3Cnx5R-u77xA@mail.gmail.com>
Message-ID: <CAAg5f2RhbPq-8_-8kgA4HCMW-6BGPsks8MB1VF36SDxDeJG9SA@mail.gmail.com>

sounds good to me, Summers.

So, that means in AGDroind we aren't yet adding any support for the
google-service.json file, but in later versions e.g. 3.x ?

On Sat, Apr 30, 2016 at 8:09 PM, Summers Pittman <supittma at redhat.com>
wrote:

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

From supittma at redhat.com  Mon May  2 06:53:18 2016
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 2 May 2016 06:53:18 -0400
Subject: [aerogear-dev] Google Service Gradle Plugin
In-Reply-To: <CAAg5f2RhbPq-8_-8kgA4HCMW-6BGPsks8MB1VF36SDxDeJG9SA@mail.gmail.com>
References: <CAEQz2CsSZRhsJqzoOaMCVuRDfmEhB22UjhHBrVDrF7gSiAN_2g@mail.gmail.com>
	<CAAg5f2RCdj-bUbLDT_e9z19A7O9Bc=gG0RBccetUUm3ja6kn0w@mail.gmail.com>
	<CAAg5f2SkYECgcJ5i6fqTjfA+2pGxmfbxg7ZQzi1ofmsRjzHixQ@mail.gmail.com>
	<CAEQz2CtsOxGs9zvoBhG1yCnpUuKksOEBqdz6SG3Cnx5R-u77xA@mail.gmail.com>
	<CAAg5f2RhbPq-8_-8kgA4HCMW-6BGPsks8MB1VF36SDxDeJG9SA@mail.gmail.com>
Message-ID: <CAEQz2CtqM8S-SWjyKsjSRP5qPvyuFP+Or-x4=FeaZ3ofjQ6=LQ@mail.gmail.com>

On Mon, May 2, 2016 at 3:16 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> sounds good to me, Summers.
>
> So, that means in AGDroind we aren't yet adding any support for the
> google-service.json file, but in later versions e.g. 3.x ?
>

Well we can support it in documentation.  Basically we can replace where we
say "Sender ID" in the docs with "Sender ID
or getString(R.string.gcm_defaultSenderId)";  This way the dev an pick what
to use (plugin or no plugin).


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

From matzew at apache.org  Mon May  2 07:33:02 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 2 May 2016 13:33:02 +0200
Subject: [aerogear-dev] Google Service Gradle Plugin
In-Reply-To: <CAEQz2CtqM8S-SWjyKsjSRP5qPvyuFP+Or-x4=FeaZ3ofjQ6=LQ@mail.gmail.com>
References: <CAEQz2CsSZRhsJqzoOaMCVuRDfmEhB22UjhHBrVDrF7gSiAN_2g@mail.gmail.com>
	<CAAg5f2RCdj-bUbLDT_e9z19A7O9Bc=gG0RBccetUUm3ja6kn0w@mail.gmail.com>
	<CAAg5f2SkYECgcJ5i6fqTjfA+2pGxmfbxg7ZQzi1ofmsRjzHixQ@mail.gmail.com>
	<CAEQz2CtsOxGs9zvoBhG1yCnpUuKksOEBqdz6SG3Cnx5R-u77xA@mail.gmail.com>
	<CAAg5f2RhbPq-8_-8kgA4HCMW-6BGPsks8MB1VF36SDxDeJG9SA@mail.gmail.com>
	<CAEQz2CtqM8S-SWjyKsjSRP5qPvyuFP+Or-x4=FeaZ3ofjQ6=LQ@mail.gmail.com>
Message-ID: <CAAg5f2TCwFFGNqn8fUcnusHJr3Xkkd-=Gri4=72Fk097ZtCoeA@mail.gmail.com>

On Mon, May 2, 2016 at 12:53 PM, Summers Pittman <supittma at redhat.com>
wrote:

>
>
> On Mon, May 2, 2016 at 3:16 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> sounds good to me, Summers.
>>
>> So, that means in AGDroind we aren't yet adding any support for the
>> google-service.json file, but in later versions e.g. 3.x ?
>>
>
> Well we can support it in documentation.  Basically we can replace where
> we say "Sender ID" in the docs with "Sender ID
> or getString(R.string.gcm_defaultSenderId)";  This way the dev an pick what
> to use (plugin or no plugin).
>

That works for me.

This also means no real code change on ADDroid 3.0.0.

Do we still want to set the Sender ID field on the UPS UI as 'deprecated'?
I think we should not do that yet, only once we have really started to the
plugin (google's or our own)

-Matthias


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

From supittma at redhat.com  Mon May  2 07:42:57 2016
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 2 May 2016 07:42:57 -0400
Subject: [aerogear-dev] Google Service Gradle Plugin
In-Reply-To: <CAAg5f2TCwFFGNqn8fUcnusHJr3Xkkd-=Gri4=72Fk097ZtCoeA@mail.gmail.com>
References: <CAEQz2CsSZRhsJqzoOaMCVuRDfmEhB22UjhHBrVDrF7gSiAN_2g@mail.gmail.com>
	<CAAg5f2RCdj-bUbLDT_e9z19A7O9Bc=gG0RBccetUUm3ja6kn0w@mail.gmail.com>
	<CAAg5f2SkYECgcJ5i6fqTjfA+2pGxmfbxg7ZQzi1ofmsRjzHixQ@mail.gmail.com>
	<CAEQz2CtsOxGs9zvoBhG1yCnpUuKksOEBqdz6SG3Cnx5R-u77xA@mail.gmail.com>
	<CAAg5f2RhbPq-8_-8kgA4HCMW-6BGPsks8MB1VF36SDxDeJG9SA@mail.gmail.com>
	<CAEQz2CtqM8S-SWjyKsjSRP5qPvyuFP+Or-x4=FeaZ3ofjQ6=LQ@mail.gmail.com>
	<CAAg5f2TCwFFGNqn8fUcnusHJr3Xkkd-=Gri4=72Fk097ZtCoeA@mail.gmail.com>
Message-ID: <CAEQz2Csz=6ikacA4xUiScv-+T-n2ghY90B6DGkSR1mNB=oVeog@mail.gmail.com>

On Mon, May 2, 2016 at 7:33 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Mon, May 2, 2016 at 12:53 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>>
>>
>> On Mon, May 2, 2016 at 3:16 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> sounds good to me, Summers.
>>>
>>> So, that means in AGDroind we aren't yet adding any support for the
>>> google-service.json file, but in later versions e.g. 3.x ?
>>>
>>
>> Well we can support it in documentation.  Basically we can replace where
>> we say "Sender ID" in the docs with "Sender ID
>> or getString(R.string.gcm_defaultSenderId)";  This way the dev an pick what
>> to use (plugin or no plugin).
>>
>
> That works for me.
>
> This also means no real code change on ADDroid 3.0.0.
>
> Do we still want to set the Sender ID field on the UPS UI as 'deprecated'?
> I think we should not do that yet, only once we have really started to the
> plugin (google's or our own)
>

I think in the UI we can mark it as "optional if using Google Services
Plugin" and change the generated code to show the sender ID or
"getString(R.string.gcm_defaultSenderId)" in the template depending on if
the sender ID is set or not.



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

From matzew at apache.org  Wed May  4 08:20:33 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 4 May 2016 14:20:33 +0200
Subject: [aerogear-dev] C-B4 changes to Aerogear
In-Reply-To: <CAAg5f2RurZbfC1wjqWLNnjm5SdJJexrU08P7TzuZ3E5XSgkU-w@mail.gmail.com>
References: <1458026557146-12395.post@n5.nabble.com>
	<CAAg5f2RurZbfC1wjqWLNnjm5SdJJexrU08P7TzuZ3E5XSgkU-w@mail.gmail.com>
Message-ID: <CAAg5f2SeQDzK=31koZ5Ls1iRQ_aR8EP7g+eQiryRzeHfdW1vtw@mail.gmail.com>

Hi Yaniv

On Tue, Mar 15, 2016 at 8:39 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> 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 :)
>

wondering if there is still interest in contributing some of this back. I
think we could get 1 -> 4 on the 1.1.x branch.
While master is on WF-10, I think only 2 -> 4 make sense there.

Any thoughts ?


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



-- 
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/20160504/14ad3537/attachment.html 

From lholmqui at redhat.com  Thu May  5 11:14:42 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 5 May 2016 11:14:42 -0400
Subject: [aerogear-dev] UnifiedPush Node sender move to Promises
Message-ID: <CALD3Fd0N2Nvq32ehMtO8UAXTBQ35uFF9Od037G9-TAgE3YpQLA@mail.gmail.com>

Hello people,

I think i would like to move the unifiedpush-node-sender,
https://github.com/aerogear/aerogear-unifiedpush-nodejs-client ,  to be
Promise based.

Currently it uses callback pattern that many node.js packages use as well
as emitting events.

When i first created this 3 years ago, that was sort of the standard way of
doing things,  but Promises have become very popular(i know i love them :))
and have been a native feature since node 0.12.x

considering we have not yet hit a 1.0.0, we can pretty much just make this
change and we will be ok.

If this is to big of a change all at once, we could always do both
callbacks and Promises.  I think we did this for Datamanager in the past.

Perhaps once we fully move to promises, then we can hit a 1.0.0

My only concern is other projects that might be using the sender that are
not yet on node 0.12 or above, since this is when promises became native.
I would really like to not have to include the polyfill.

i suppose those users would need to stick to the previous versions then.

anyway,  would like to hear some thoughts.


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

From matzew at apache.org  Thu May  5 13:37:47 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 5 May 2016 19:37:47 +0200
Subject: [aerogear-dev] [Aerogear-users] UnifiedPush Node sender move to
	Promises
In-Reply-To: <CALD3Fd0N2Nvq32ehMtO8UAXTBQ35uFF9Od037G9-TAgE3YpQLA@mail.gmail.com>
References: <CALD3Fd0N2Nvq32ehMtO8UAXTBQ35uFF9Od037G9-TAgE3YpQLA@mail.gmail.com>
Message-ID: <CAAg5f2SdUCCXKRf3Ktdhs0JZHSr5OjtxJC24Fngz+XY5Noe_qw@mail.gmail.com>

I think it would be good for the community to move forward and use latest
technology. Node 0.12 is already very old, given the current version is 6.

How about getting promisses in, and afterwards release this as a 1.0.0
release ?

On Thu, May 5, 2016 at 5:14 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> Hello people,
>
> I think i would like to move the unifiedpush-node-sender,
> https://github.com/aerogear/aerogear-unifiedpush-nodejs-client ,  to be
> Promise based.
>
> Currently it uses callback pattern that many node.js packages use as well
> as emitting events.
>
> When i first created this 3 years ago, that was sort of the standard way
> of doing things,  but Promises have become very popular(i know i love them
> :)) and have been a native feature since node 0.12.x
>
> considering we have not yet hit a 1.0.0, we can pretty much just make this
> change and we will be ok.
>
> If this is to big of a change all at once, we could always do both
> callbacks and Promises.  I think we did this for Datamanager in the past.
>
> Perhaps once we fully move to promises, then we can hit a 1.0.0
>
> My only concern is other projects that might be using the sender that are
> not yet on node 0.12 or above, since this is when promises became native.
> I would really like to not have to include the polyfill.
>
> i suppose those users would need to stick to the previous versions then.
>
> anyway,  would like to hear some thoughts.
>
>
> -Luke
>
>
>
>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>


-- 
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/20160505/03863383/attachment.html 

From lholmqui at redhat.com  Thu May  5 13:42:52 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 5 May 2016 13:42:52 -0400
Subject: [aerogear-dev] [Aerogear-users] UnifiedPush Node sender move to
	Promises
In-Reply-To: <CAAg5f2SdUCCXKRf3Ktdhs0JZHSr5OjtxJC24Fngz+XY5Noe_qw@mail.gmail.com>
References: <CALD3Fd0N2Nvq32ehMtO8UAXTBQ35uFF9Od037G9-TAgE3YpQLA@mail.gmail.com>
	<CAAg5f2SdUCCXKRf3Ktdhs0JZHSr5OjtxJC24Fngz+XY5Noe_qw@mail.gmail.com>
Message-ID: <CALD3Fd0a7+gk4dV6ABvj=6-XWh0+qBg_qmAY62jTay1NnCvABw@mail.gmail.com>

On Thu, May 5, 2016 at 1:37 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> I think it would be good for the community to move forward and use latest
> technology. Node 0.12 is already very old, given the current version is 6.
>
> How about getting promisses in, and afterwards release this as a 1.0.0
> release ?
>

i think this sounds like a plan,

/me goes and creates a JIRA

>
> On Thu, May 5, 2016 at 5:14 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> Hello people,
>>
>> I think i would like to move the unifiedpush-node-sender,
>> https://github.com/aerogear/aerogear-unifiedpush-nodejs-client ,  to be
>> Promise based.
>>
>> Currently it uses callback pattern that many node.js packages use as well
>> as emitting events.
>>
>> When i first created this 3 years ago, that was sort of the standard way
>> of doing things,  but Promises have become very popular(i know i love them
>> :)) and have been a native feature since node 0.12.x
>>
>> considering we have not yet hit a 1.0.0, we can pretty much just make
>> this change and we will be ok.
>>
>> If this is to big of a change all at once, we could always do both
>> callbacks and Promises.  I think we did this for Datamanager in the past.
>>
>> Perhaps once we fully move to promises, then we can hit a 1.0.0
>>
>> My only concern is other projects that might be using the sender that are
>> not yet on node 0.12 or above, since this is when promises became native.
>> I would really like to not have to include the polyfill.
>>
>> i suppose those users would need to stick to the previous versions then.
>>
>> anyway,  would like to hear some thoughts.
>>
>>
>> -Luke
>>
>>
>>
>>
>>
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160505/7b3e69c9/attachment-0001.html 

From lholmqui at redhat.com  Thu May  5 13:46:15 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 5 May 2016 13:46:15 -0400
Subject: [aerogear-dev] [Aerogear-users] UnifiedPush Node sender move to
	Promises
In-Reply-To: <CALD3Fd0a7+gk4dV6ABvj=6-XWh0+qBg_qmAY62jTay1NnCvABw@mail.gmail.com>
References: <CALD3Fd0N2Nvq32ehMtO8UAXTBQ35uFF9Od037G9-TAgE3YpQLA@mail.gmail.com>
	<CAAg5f2SdUCCXKRf3Ktdhs0JZHSr5OjtxJC24Fngz+XY5Noe_qw@mail.gmail.com>
	<CALD3Fd0a7+gk4dV6ABvj=6-XWh0+qBg_qmAY62jTay1NnCvABw@mail.gmail.com>
Message-ID: <CALD3Fd1=F65fEFUoCdFWzxLGU4hmV3fosutUgzO6YpyW4H96Ow@mail.gmail.com>

for those following along at home:

https://issues.jboss.org/browse/AGPUSH-1621

On Thu, May 5, 2016 at 1:42 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

>
>
> On Thu, May 5, 2016 at 1:37 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> I think it would be good for the community to move forward and use latest
>> technology. Node 0.12 is already very old, given the current version is 6.
>>
>> How about getting promisses in, and afterwards release this as a 1.0.0
>> release ?
>>
>
> i think this sounds like a plan,
>
> /me goes and creates a JIRA
>
>>
>> On Thu, May 5, 2016 at 5:14 PM, Luke Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>> Hello people,
>>>
>>> I think i would like to move the unifiedpush-node-sender,
>>> https://github.com/aerogear/aerogear-unifiedpush-nodejs-client ,  to be
>>> Promise based.
>>>
>>> Currently it uses callback pattern that many node.js packages use as
>>> well as emitting events.
>>>
>>> When i first created this 3 years ago, that was sort of the standard way
>>> of doing things,  but Promises have become very popular(i know i love them
>>> :)) and have been a native feature since node 0.12.x
>>>
>>> considering we have not yet hit a 1.0.0, we can pretty much just make
>>> this change and we will be ok.
>>>
>>> If this is to big of a change all at once, we could always do both
>>> callbacks and Promises.  I think we did this for Datamanager in the past.
>>>
>>> Perhaps once we fully move to promises, then we can hit a 1.0.0
>>>
>>> My only concern is other projects that might be using the sender that
>>> are not yet on node 0.12 or above, since this is when promises became
>>> native.  I would really like to not have to include the polyfill.
>>>
>>> i suppose those users would need to stick to the previous versions then.
>>>
>>> anyway,  would like to hear some thoughts.
>>>
>>>
>>> -Luke
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Aerogear-users mailing list
>>> Aerogear-users at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>>
>>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160505/e921bb9b/attachment.html 

From matzew at apache.org  Fri May  6 03:38:35 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 6 May 2016 09:38:35 +0200
Subject: [aerogear-dev] AGDroid 3.0.0 status
Message-ID: <CAAg5f2THoaEOT4F4z6iMVTW4BnGs_-w3RM7EaAJ4=oVAEzqMgg@mail.gmail.com>

Hi,

now that the GCM 3 related JIRAs are merged, I did take a look at the left
items for 3.0.0

https://issues.jboss.org/projects/AGDROID/versions/12327585

I think we need to address these two, as they change APIs
* https://issues.jboss.org/browse/AGDROID-504
* https://issues.jboss.org/browse/AGDROID-421

Once the version is out this one needs to be done too:
* https://issues.jboss.org/browse/AGDROID-534

Any thoughts ?

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/20160506/97a04fa3/attachment.html 

From lholmqui at redhat.com  Mon May  9 16:19:03 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Mon, 9 May 2016 16:19:03 -0400
Subject: [aerogear-dev] deploy failure for Master
Message-ID: <CALD3Fd2ZMbDAosdSFYkFqn4hFJy-TrHj7Y6M3qbFnoH6wWv_bg@mail.gmail.com>

so i'm trying to deploy what is currently on master to wildfly 9(also tried
10) and i'm getting this error:

https://gist.github.com/lholmquist/6743191e4c4f225dac7e8e16e86f09fc


i've copied the h2 db deployment script to the wildly deployment
directory,  manually copied the  auth-server and ag-push war files to the
wildlfy deployment directory from their respective target directories,

started with "./bin/standalone.sh -c standalone-full.xml -b 0.0.0.0"

perhaps i'm missing a step?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160509/b7f51bea/attachment.html 

From matzew at apache.org  Tue May 10 00:11:14 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 10 May 2016 06:11:14 +0200
Subject: [aerogear-dev] deploy failure for Master
In-Reply-To: <CALD3Fd2ZMbDAosdSFYkFqn4hFJy-TrHj7Y6M3qbFnoH6wWv_bg@mail.gmail.com>
References: <CALD3Fd2ZMbDAosdSFYkFqn4hFJy-TrHj7Y6M3qbFnoH6wWv_bg@mail.gmail.com>
Message-ID: <CAAg5f2S9SphzfsS60cFAKJRVyWjPAXbL_J_oEefsi4r4x7F24Q@mail.gmail.com>

Hi Luke,

besides the DB CLI, you need to configure JMS, using this CLI:
https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/configuration

Note, the JMS bits are tied to WF-10.


On Mon, May 9, 2016 at 10:19 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> so i'm trying to deploy what is currently on master to wildfly 9(also
> tried 10) and i'm getting this error:
>
> https://gist.github.com/lholmquist/6743191e4c4f225dac7e8e16e86f09fc
>
>
> i've copied the h2 db deployment script to the wildly deployment
> directory,  manually copied the  auth-server and ag-push war files to the
> wildlfy deployment directory from their respective target directories,
>
> started with "./bin/standalone.sh -c standalone-full.xml -b 0.0.0.0"
>
> perhaps i'm missing a step?
>
> _______________________________________________
> 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/20160510/27b3235f/attachment.html 

From lholmqui at redhat.com  Tue May 10 08:39:48 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Tue, 10 May 2016 08:39:48 -0400
Subject: [aerogear-dev] [Aerogear-users]  deploy failure for Master
In-Reply-To: <CAAg5f2S9SphzfsS60cFAKJRVyWjPAXbL_J_oEefsi4r4x7F24Q@mail.gmail.com>
References: <CALD3Fd2ZMbDAosdSFYkFqn4hFJy-TrHj7Y6M3qbFnoH6wWv_bg@mail.gmail.com>
	<CAAg5f2S9SphzfsS60cFAKJRVyWjPAXbL_J_oEefsi4r4x7F24Q@mail.gmail.com>
Message-ID: <CALD3Fd0xvzuoCWbUEa_S=Yp6CsXVFbzivioJJ2RBOGxCHeOVSQ@mail.gmail.com>

ah yes, that did it.

I suppose i should have RTFM,  i usually look at the readme on GH, i'm
wondering if there should be something there also?

On Tue, May 10, 2016 at 12:11 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi Luke,
>
> besides the DB CLI, you need to configure JMS, using this CLI:
>
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/configuration
>
> Note, the JMS bits are tied to WF-10.
>
>
> On Mon, May 9, 2016 at 10:19 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> so i'm trying to deploy what is currently on master to wildfly 9(also
>> tried 10) and i'm getting this error:
>>
>> https://gist.github.com/lholmquist/6743191e4c4f225dac7e8e16e86f09fc
>>
>>
>> i've copied the h2 db deployment script to the wildly deployment
>> directory,  manually copied the  auth-server and ag-push war files to the
>> wildlfy deployment directory from their respective target directories,
>>
>> started with "./bin/standalone.sh -c standalone-full.xml -b 0.0.0.0"
>>
>> perhaps i'm missing a step?
>>
>> _______________________________________________
>> 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-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160510/abf873e4/attachment-0001.html 

From matzew at apache.org  Tue May 10 09:08:34 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 10 May 2016 15:08:34 +0200
Subject: [aerogear-dev] [Aerogear-users] deploy failure for Master
In-Reply-To: <CALD3Fd0xvzuoCWbUEa_S=Yp6CsXVFbzivioJJ2RBOGxCHeOVSQ@mail.gmail.com>
References: <CALD3Fd2ZMbDAosdSFYkFqn4hFJy-TrHj7Y6M3qbFnoH6wWv_bg@mail.gmail.com>
	<CAAg5f2S9SphzfsS60cFAKJRVyWjPAXbL_J_oEefsi4r4x7F24Q@mail.gmail.com>
	<CALD3Fd0xvzuoCWbUEa_S=Yp6CsXVFbzivioJJ2RBOGxCHeOVSQ@mail.gmail.com>
Message-ID: <CAAg5f2RXvLA61Gka9y9+3F4k1gyx3V5QwipzX5HcoBEixupUVw@mail.gmail.com>

yes, I think the two CLI scripts all should go into a common config folder,
and some text needs to be eventually on the guide

On Tue, May 10, 2016 at 2:39 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> ah yes, that did it.
>
> I suppose i should have RTFM,  i usually look at the readme on GH, i'm
> wondering if there should be something there also?
>
> On Tue, May 10, 2016 at 12:11 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi Luke,
>>
>> besides the DB CLI, you need to configure JMS, using this CLI:
>>
>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/configuration
>>
>> Note, the JMS bits are tied to WF-10.
>>
>>
>> On Mon, May 9, 2016 at 10:19 PM, Luke Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>> so i'm trying to deploy what is currently on master to wildfly 9(also
>>> tried 10) and i'm getting this error:
>>>
>>> https://gist.github.com/lholmquist/6743191e4c4f225dac7e8e16e86f09fc
>>>
>>>
>>> i've copied the h2 db deployment script to the wildly deployment
>>> directory,  manually copied the  auth-server and ag-push war files to the
>>> wildlfy deployment directory from their respective target directories,
>>>
>>> started with "./bin/standalone.sh -c standalone-full.xml -b 0.0.0.0"
>>>
>>> perhaps i'm missing a step?
>>>
>>> _______________________________________________
>>> 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-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>
> _______________________________________________
> 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/20160510/796c19ec/attachment.html 

From matzew at apache.org  Tue May 10 15:54:41 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 10 May 2016 21:54:41 +0200
Subject: [aerogear-dev] GCM push - MismatchSenderId
Message-ID: <CAAg5f2QBZS7Tik7aT7eitgUz=nCz70TahT93L5v37AXU0_bhhw@mail.gmail.com>

Hi,

I added a fake token for testing, and I am seeing this in the logs:

Processing [MismatchSenderId] error code from GCM response, for
registration ID:
[APA91bGVJjnqOASDasFAFDSFASDSFADFSDAAFSDFDSmU5NyLGOsiumWyN62BjE8FCVvYscnKzZrokIYadsadsasADas_s45cUnxdJEVrBokHX5k0fewfoV2JD17GUx5s5]

I was guessing that we do remove these tokens, but no... IMO this should be
fixed that, no ?

-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/20160510/eb88e4d0/attachment.html 

From matzew at apache.org  Tue May 10 16:03:56 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 10 May 2016 22:03:56 +0200
Subject: [aerogear-dev] GCM push - MismatchSenderId
In-Reply-To: <CAAg5f2QBZS7Tik7aT7eitgUz=nCz70TahT93L5v37AXU0_bhhw@mail.gmail.com>
References: <CAAg5f2QBZS7Tik7aT7eitgUz=nCz70TahT93L5v37AXU0_bhhw@mail.gmail.com>
Message-ID: <CAAg5f2QQ9-HTbrrXBCh_jbcr6Ok9o7r=hN=FWP8sfv_NoofLUQ@mail.gmail.com>

PR: https://github.com/aerogear/aerogear-unifiedpush-server/pull/715

On Tue, May 10, 2016 at 9:54 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> I added a fake token for testing, and I am seeing this in the logs:
>
> Processing [MismatchSenderId] error code from GCM response, for
> registration ID:
> [APA91bGVJjnqOASDasFAFDSFASDSFADFSDAAFSDFDSmU5NyLGOsiumWyN62BjE8FCVvYscnKzZrokIYadsadsasADas_s45cUnxdJEVrBokHX5k0fewfoV2JD17GUx5s5]
>
> I was guessing that we do remove these tokens, but no... IMO this should
> be fixed that, no ?
>
> -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/20160510/1b4b0160/attachment.html 

From matzew at apache.org  Wed May 11 08:55:59 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 11 May 2016 14:55:59 +0200
Subject: [aerogear-dev] aerogear-crytpo-java
Message-ID: <CAAg5f2SmvLTXm8YbriWJs-Z9OPcSW7cr3fbdzsY=drze_R8yTQ@mail.gmail.com>

Hi,

the 0.1.6 repo is staged here:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8211/

mainly containing fixes from summers, for Android

-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/20160511/4f915729/attachment.html 

From supittma at redhat.com  Wed May 11 09:42:40 2016
From: supittma at redhat.com (Summers Pittman)
Date: Wed, 11 May 2016 09:42:40 -0400
Subject: [aerogear-dev] aerogear-crytpo-java
In-Reply-To: <CAAg5f2SmvLTXm8YbriWJs-Z9OPcSW7cr3fbdzsY=drze_R8yTQ@mail.gmail.com>
References: <CAAg5f2SmvLTXm8YbriWJs-Z9OPcSW7cr3fbdzsY=drze_R8yTQ@mail.gmail.com>
Message-ID: <CAEQz2CuY=MrYNBScBpkg7oWBm6jqgqV2tV82gR9peHZOCr_fJA@mail.gmail.com>

I think you are missing the android classified artifact

See :
http://repo1.maven.org/maven2/org/jboss/aerogear/aerogear-crypto/0.1.5/

Vs :
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8211/org/jboss/aerogear/aerogear-crypto/0.1.6/

On Wed, May 11, 2016 at 8:55 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> the 0.1.6 repo is staged here:
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8211/
>
> mainly containing fixes from summers, for Android
>
> -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/20160511/506fbc48/attachment-0001.html 

From supittma at redhat.com  Wed May 11 10:01:31 2016
From: supittma at redhat.com (Summers Pittman)
Date: Wed, 11 May 2016 10:01:31 -0400
Subject: [aerogear-dev] aerogear-crytpo-java
In-Reply-To: <CAEQz2CuY=MrYNBScBpkg7oWBm6jqgqV2tV82gR9peHZOCr_fJA@mail.gmail.com>
References: <CAAg5f2SmvLTXm8YbriWJs-Z9OPcSW7cr3fbdzsY=drze_R8yTQ@mail.gmail.com>
	<CAEQz2CuY=MrYNBScBpkg7oWBm6jqgqV2tV82gR9peHZOCr_fJA@mail.gmail.com>
Message-ID: <CAEQz2CsPaB8CJE=b_MCD1STi3OR=TmqVO8JGKTMD4UcwrsuBgw@mail.gmail.com>

https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8213/
is happy

On Wed, May 11, 2016 at 9:42 AM, Summers Pittman <supittma at redhat.com>
wrote:

> I think you are missing the android classified artifact
>
> See :
> http://repo1.maven.org/maven2/org/jboss/aerogear/aerogear-crypto/0.1.5/
>
> Vs :
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8211/org/jboss/aerogear/aerogear-crypto/0.1.6/
>
> On Wed, May 11, 2016 at 8:55 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> the 0.1.6 repo is staged here:
>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8211/
>>
>> mainly containing fixes from summers, for Android
>>
>> -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/20160511/4057c1f5/attachment.html 

From matzew at apache.org  Wed May 11 12:14:53 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 11 May 2016 18:14:53 +0200
Subject: [aerogear-dev] Android - 3.0.0 bits
Message-ID: <CAAg5f2SMXGn5CTGkhjkN0PbyGd0+UGnoLY8qpgV==pe2JQmF1g@mail.gmail.com>

Hi,

after some time, we got a new release staged, 3.0.0. Most relevant target
is GCM-3 features, as long as InstanceID for GCM token regitration, as
GCM.register is deprecated.

Besides that there are some more changes in, e.g. an API change on our
-store module.

Full details are visible in JIRA:
https://issues.jboss.org/projects/AGDROID/versions/12327585

The staging repo is located here:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8215/

Have fun testing it.
-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/20160511/6fdf7b02/attachment.html 

From matzew at apache.org  Wed May 11 14:48:52 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 11 May 2016 20:48:52 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.3.Final
Message-ID: <CAAg5f2R1e3F+KoXwRmYs=za3=YVdkoJdgL9f3xaMs8hqKa_fPg@mail.gmail.com>

Hello there!

for the 1.1.x series we are releasing 1.1.3.Final.

Biggest focus for this release was GCM-3 APIs for Android push. A full list
of all changes is listed here:
https://issues.jboss.org/projects/AGPUSH/versions/12330260

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

A pre-release is available on github as well:
https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.1.3.Final

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

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/20160511/17a59458/attachment.html 

From matzew at apache.org  Wed May 11 14:56:42 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 11 May 2016 20:56:42 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.3.Final
In-Reply-To: <CAAg5f2R1e3F+KoXwRmYs=za3=YVdkoJdgL9f3xaMs8hqKa_fPg@mail.gmail.com>
References: <CAAg5f2R1e3F+KoXwRmYs=za3=YVdkoJdgL9f3xaMs8hqKa_fPg@mail.gmail.com>
Message-ID: <CAAg5f2Sn3SXPoTn572yM0Fg+jWZfN9BFRDA9QEqdpcgtn2kOfA@mail.gmail.com>

The 1.1.x dockerfiles are now also updated:
https://github.com/aerogear/dockerfiles/pull/17

On Wed, May 11, 2016 at 8:48 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hello there!
>
> for the 1.1.x series we are releasing 1.1.3.Final.
>
> Biggest focus for this release was GCM-3 APIs for Android push. A full
> list of all changes is listed here:
> https://issues.jboss.org/projects/AGPUSH/versions/12330260
>
> You can find the staging repository here:
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8216/
>
> A pre-release is available on github as well:
>
> https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.1.3.Final
>
> Please give it a try over the next few days, so that we can release it!
>
> Thanks,
> Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160511/10396c72/attachment.html 

From matzew at apache.org  Thu May 12 03:15:41 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 12 May 2016 09:15:41 +0200
Subject: [aerogear-dev] aerogear-crytpo-java
In-Reply-To: <CAEQz2CsPaB8CJE=b_MCD1STi3OR=TmqVO8JGKTMD4UcwrsuBgw@mail.gmail.com>
References: <CAAg5f2SmvLTXm8YbriWJs-Z9OPcSW7cr3fbdzsY=drze_R8yTQ@mail.gmail.com>
	<CAEQz2CuY=MrYNBScBpkg7oWBm6jqgqV2tV82gR9peHZOCr_fJA@mail.gmail.com>
	<CAEQz2CsPaB8CJE=b_MCD1STi3OR=TmqVO8JGKTMD4UcwrsuBgw@mail.gmail.com>
Message-ID: <CAAg5f2Qks=mSEmw2kCK5d6OkrnvOXM=n-9qnMvqvcHc04_Edgg@mail.gmail.com>

clicked the button \o/

On Wed, May 11, 2016 at 4:01 PM, Summers Pittman <supittma at redhat.com>
wrote:

>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8213/
> is happy
>
> On Wed, May 11, 2016 at 9:42 AM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> I think you are missing the android classified artifact
>>
>> See :
>> http://repo1.maven.org/maven2/org/jboss/aerogear/aerogear-crypto/0.1.5/
>>
>> Vs :
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8211/org/jboss/aerogear/aerogear-crypto/0.1.6/
>>
>> On Wed, May 11, 2016 at 8:55 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> the 0.1.6 repo is staged here:
>>>
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8211/
>>>
>>> mainly containing fixes from summers, for Android
>>>
>>> -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
>>>
>>
>>
>
> _______________________________________________
> 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/20160512/c509fedd/attachment-0001.html 

From matzew at apache.org  Thu May 12 07:19:58 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 12 May 2016 13:19:58 +0200
Subject: [aerogear-dev] aerogear-crytpo-java
In-Reply-To: <CAAg5f2Qks=mSEmw2kCK5d6OkrnvOXM=n-9qnMvqvcHc04_Edgg@mail.gmail.com>
References: <CAAg5f2SmvLTXm8YbriWJs-Z9OPcSW7cr3fbdzsY=drze_R8yTQ@mail.gmail.com>
	<CAEQz2CuY=MrYNBScBpkg7oWBm6jqgqV2tV82gR9peHZOCr_fJA@mail.gmail.com>
	<CAEQz2CsPaB8CJE=b_MCD1STi3OR=TmqVO8JGKTMD4UcwrsuBgw@mail.gmail.com>
	<CAAg5f2Qks=mSEmw2kCK5d6OkrnvOXM=n-9qnMvqvcHc04_Edgg@mail.gmail.com>
Message-ID: <CAAg5f2RBaQEhSEzJ5MKmmbiH47sLdkg_JjJTxhu8rUA-hdaSxQ@mail.gmail.com>

It's out in the wild:

http://repo1.maven.org/maven2/org/jboss/aerogear/aerogear-crypto/0.1.6/

On Thu, May 12, 2016 at 9:15 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> clicked the button \o/
>
> On Wed, May 11, 2016 at 4:01 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8213/
>> is happy
>>
>> On Wed, May 11, 2016 at 9:42 AM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>> I think you are missing the android classified artifact
>>>
>>> See :
>>> http://repo1.maven.org/maven2/org/jboss/aerogear/aerogear-crypto/0.1.5/
>>>
>>> Vs :
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8211/org/jboss/aerogear/aerogear-crypto/0.1.6/
>>>
>>> On Wed, May 11, 2016 at 8:55 AM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> the 0.1.6 repo is staged here:
>>>>
>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8211/
>>>>
>>>> mainly containing fixes from summers, for Android
>>>>
>>>> -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
>>>>
>>>
>>>
>>
>> _______________________________________________
>> 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/20160512/9bc4b95f/attachment.html 

From lholmqui at redhat.com  Thu May 12 14:26:37 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 12 May 2016 14:26:37 -0400
Subject: [aerogear-dev] admin REST client for node
Message-ID: <CALD3Fd1oTjnx8QmgCeUa3t_Lsm_c=rsx2LfH0xysk3fkBBBt_w@mail.gmail.com>

https://www.npmjs.com/package/unifiedpush-admin-client

I remember a little while back someone created an admin client in Java,  so
i decided to start one in node.js

ATM for the 0.1.0 release,  i've only implemented the CRUD for
applications, following these docs
https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/#838429674


The only thing i need to do to get "authenitcated" with keycloak was to
switch direct access grants to on in the "unifiedpush-server-js" client.
it also assumes that you are using the coupled KC/UPS bundle. which i think
is the only way right now.


once they become decoupled, then i can modify the client accordingly.

The tests are currently just mocking what the ups would return.  I would
like to get some integration tests setup, but i'm not to sure how to
automate the "turning on" of the direct access grants.

i could probably use docker for the sever setup

anyway,  here it is  :) and more functionality to come

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

From supittma at redhat.com  Thu May 12 16:11:08 2016
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 12 May 2016 16:11:08 -0400
Subject: [aerogear-dev] Android - 3.0.0 bits
In-Reply-To: <CAAg5f2SMXGn5CTGkhjkN0PbyGd0+UGnoLY8qpgV==pe2JQmF1g@mail.gmail.com>
References: <CAAg5f2SMXGn5CTGkhjkN0PbyGd0+UGnoLY8qpgV==pe2JQmF1g@mail.gmail.com>
Message-ID: <CAEQz2Cs06OHoayTfcbp8MYWbUGGNNDktaqOCerYYg80arLdCGw@mail.gmail.com>

I found one bug while testing.

The pipe module uses reflection to build requests in a way that doesn't
always work with instant run (a great feature of Android Studio 2.0).
There is an open PR for this.

https://github.com/aerogear/aerogear-android-pipe/pull/47

On Wed, May 11, 2016 at 12:14 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> after some time, we got a new release staged, 3.0.0. Most relevant target
> is GCM-3 features, as long as InstanceID for GCM token regitration, as
> GCM.register is deprecated.
>
> Besides that there are some more changes in, e.g. an API change on our
> -store module.
>
> Full details are visible in JIRA:
> https://issues.jboss.org/projects/AGDROID/versions/12327585
>
> The staging repo is located here:
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8215/
>
> Have fun testing it.
> -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/20160512/ddd8635b/attachment.html 

From matzew at apache.org  Thu May 12 16:40:39 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 12 May 2016 22:40:39 +0200
Subject: [aerogear-dev] Android - 3.0.0 bits
In-Reply-To: <CAEQz2Cs06OHoayTfcbp8MYWbUGGNNDktaqOCerYYg80arLdCGw@mail.gmail.com>
References: <CAAg5f2SMXGn5CTGkhjkN0PbyGd0+UGnoLY8qpgV==pe2JQmF1g@mail.gmail.com>
	<CAEQz2Cs06OHoayTfcbp8MYWbUGGNNDktaqOCerYYg80arLdCGw@mail.gmail.com>
Message-ID: <CAAg5f2R7MdaTVthWdRLjRT0Ne686OnSGNruB_mDki8Stnu_SBw@mail.gmail.com>

Thanks for tessting.

I've deleted the broken pipe from teh 8215 repo, and have updated the
version on a separate repo:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8220/
 (this includes only the fixed -pipe:3.0.0)

-Matthias

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

> I found one bug while testing.
>
> The pipe module uses reflection to build requests in a way that doesn't
> always work with instant run (a great feature of Android Studio 2.0).
> There is an open PR for this.
>
> https://github.com/aerogear/aerogear-android-pipe/pull/47
>
> On Wed, May 11, 2016 at 12:14 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> after some time, we got a new release staged, 3.0.0. Most relevant target
>> is GCM-3 features, as long as InstanceID for GCM token regitration, as
>> GCM.register is deprecated.
>>
>> Besides that there are some more changes in, e.g. an API change on our
>> -store module.
>>
>> Full details are visible in JIRA:
>> https://issues.jboss.org/projects/AGDROID/versions/12327585
>>
>> The staging repo is located here:
>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8215/
>>
>> Have fun testing it.
>> -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
>>
>
>
> _______________________________________________
> 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/20160512/a51cf607/attachment-0001.html 

From supittma at redhat.com  Thu May 12 16:45:41 2016
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 12 May 2016 16:45:41 -0400
Subject: [aerogear-dev] Android - 3.0.0 bits
In-Reply-To: <CAAg5f2R7MdaTVthWdRLjRT0Ne686OnSGNruB_mDki8Stnu_SBw@mail.gmail.com>
References: <CAAg5f2SMXGn5CTGkhjkN0PbyGd0+UGnoLY8qpgV==pe2JQmF1g@mail.gmail.com>
	<CAEQz2Cs06OHoayTfcbp8MYWbUGGNNDktaqOCerYYg80arLdCGw@mail.gmail.com>
	<CAAg5f2R7MdaTVthWdRLjRT0Ne686OnSGNruB_mDki8Stnu_SBw@mail.gmail.com>
Message-ID: <CAEQz2CsJnCrUiTh3GSN0-obUdo32YXYs59MnoL48nbGS19D8Nw@mail.gmail.com>

Passes a quick smoke test.

On Thu, May 12, 2016 at 4:40 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Thanks for tessting.
>
> I've deleted the broken pipe from teh 8215 repo, and have updated the
> version on a separate repo:
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8220/
>  (this includes only the fixed -pipe:3.0.0)
>
> -Matthias
>
> On Thu, May 12, 2016 at 10:11 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> I found one bug while testing.
>>
>> The pipe module uses reflection to build requests in a way that doesn't
>> always work with instant run (a great feature of Android Studio 2.0).
>> There is an open PR for this.
>>
>> https://github.com/aerogear/aerogear-android-pipe/pull/47
>>
>> On Wed, May 11, 2016 at 12:14 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> after some time, we got a new release staged, 3.0.0. Most relevant
>>> target is GCM-3 features, as long as InstanceID for GCM token regitration,
>>> as GCM.register is deprecated.
>>>
>>> Besides that there are some more changes in, e.g. an API change on our
>>> -store module.
>>>
>>> Full details are visible in JIRA:
>>> https://issues.jboss.org/projects/AGDROID/versions/12327585
>>>
>>> The staging repo is located here:
>>>
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8215/
>>>
>>> Have fun testing it.
>>> -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
>>>
>>
>>
>> _______________________________________________
>> 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/20160512/8ca52a56/attachment.html 

From matzew at apache.org  Thu May 12 16:47:38 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 12 May 2016 22:47:38 +0200
Subject: [aerogear-dev] Android - 3.0.0 bits
In-Reply-To: <CAEQz2CsJnCrUiTh3GSN0-obUdo32YXYs59MnoL48nbGS19D8Nw@mail.gmail.com>
References: <CAAg5f2SMXGn5CTGkhjkN0PbyGd0+UGnoLY8qpgV==pe2JQmF1g@mail.gmail.com>
	<CAEQz2Cs06OHoayTfcbp8MYWbUGGNNDktaqOCerYYg80arLdCGw@mail.gmail.com>
	<CAAg5f2R7MdaTVthWdRLjRT0Ne686OnSGNruB_mDki8Stnu_SBw@mail.gmail.com>
	<CAEQz2CsJnCrUiTh3GSN0-obUdo32YXYs59MnoL48nbGS19D8Nw@mail.gmail.com>
Message-ID: <CAAg5f2R88VE38W9cGwdKkZ=v3onwYRM7UBBAFpQCy0sApFimEg@mail.gmail.com>

shipping....

On Thu, May 12, 2016 at 10:45 PM, Summers Pittman <supittma at redhat.com>
wrote:

> Passes a quick smoke test.
>
> On Thu, May 12, 2016 at 4:40 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Thanks for tessting.
>>
>> I've deleted the broken pipe from teh 8215 repo, and have updated the
>> version on a separate repo:
>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8220/
>>  (this includes only the fixed -pipe:3.0.0)
>>
>> -Matthias
>>
>> On Thu, May 12, 2016 at 10:11 PM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>> I found one bug while testing.
>>>
>>> The pipe module uses reflection to build requests in a way that doesn't
>>> always work with instant run (a great feature of Android Studio 2.0).
>>> There is an open PR for this.
>>>
>>> https://github.com/aerogear/aerogear-android-pipe/pull/47
>>>
>>> On Wed, May 11, 2016 at 12:14 PM, Matthias Wessendorf <matzew at apache.org
>>> > wrote:
>>>
>>>> Hi,
>>>>
>>>> after some time, we got a new release staged, 3.0.0. Most relevant
>>>> target is GCM-3 features, as long as InstanceID for GCM token regitration,
>>>> as GCM.register is deprecated.
>>>>
>>>> Besides that there are some more changes in, e.g. an API change on our
>>>> -store module.
>>>>
>>>> Full details are visible in JIRA:
>>>> https://issues.jboss.org/projects/AGDROID/versions/12327585
>>>>
>>>> The staging repo is located here:
>>>>
>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8215/
>>>>
>>>> Have fun testing it.
>>>> -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
>>>>
>>>
>>>
>>> _______________________________________________
>>> 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/20160512/f66a6dc6/attachment.html 

From matzew at apache.org  Fri May 13 02:20:20 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 13 May 2016 08:20:20 +0200
Subject: [aerogear-dev] Travis CI failing for android-pipe
Message-ID: <CAAg5f2R9gO0Qxvq3jtz6uTcWA21CFytNeiFxCYdbMNTXaERVzA@mail.gmail.com>

Hi,

locally all works fine, otherwise the release plugin would not have allowed
me to stage (and release) the bits.

However, on Travis, I am getting a weird error from the
'com.simpligility.maven.plugins:android-maven-plugin' plugin:


[INFO]

[INFO]
------------------------------------------------------------------------
[INFO] Building AeroGear Android Pipe Test 3.0.0
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- android-maven-plugin:4.4.1:instrument (default-cli) @
aerogear-android-pipe-test ---
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 5.821 s
[INFO] Finished at: 2016-05-13T06:15:22+00:00
[INFO] Final Memory: 24M/491M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
com.simpligility.maven.plugins:android-maven-plugin:4.4.1:instrument
(default-cli) on project aerogear-android-pipe-test: Execution default-cli
of goal
com.simpligility.maven.plugins:android-maven-plugin:4.4.1:instrument
failed: java.io.FileNotFoundException:
/home/travis/build/aerogear/aerogear-android-pipe/aerogear-android-pipe-test/target/AndroidManifest.xml
(No such file or directory) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException




and yes, locally there is the
'aerogear-android-pipe/aerogear-android-pipe-test/target/AndroidManifest.xml'
file in question.

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/20160513/4f0f5d4e/attachment-0001.html 

From matzew at apache.org  Fri May 13 02:21:59 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 13 May 2016 08:21:59 +0200
Subject: [aerogear-dev] Android - 3.0.0 bits
In-Reply-To: <CAAg5f2R88VE38W9cGwdKkZ=v3onwYRM7UBBAFpQCy0sApFimEg@mail.gmail.com>
References: <CAAg5f2SMXGn5CTGkhjkN0PbyGd0+UGnoLY8qpgV==pe2JQmF1g@mail.gmail.com>
	<CAEQz2Cs06OHoayTfcbp8MYWbUGGNNDktaqOCerYYg80arLdCGw@mail.gmail.com>
	<CAAg5f2R7MdaTVthWdRLjRT0Ne686OnSGNruB_mDki8Stnu_SBw@mail.gmail.com>
	<CAEQz2CsJnCrUiTh3GSN0-obUdo32YXYs59MnoL48nbGS19D8Nw@mail.gmail.com>
	<CAAg5f2R88VE38W9cGwdKkZ=v3onwYRM7UBBAFpQCy0sApFimEg@mail.gmail.com>
Message-ID: <CAAg5f2QuTcAsF3Gdh_wJvPFCT+QMESe+f6RJ-Th_+q2+dym8DA@mail.gmail.com>

Hi,  the JARs did hit maven central:

http://repo1.maven.org/maven2/org/jboss/aerogear/aerogear-android-core/3.0.0/
http://repo1.maven.org/maven2/org/jboss/aerogear/aerogear-android-pipe/3.0.0/
http://repo1.maven.org/maven2/org/jboss/aerogear/aerogear-android-push/3.0.0/
http://repo1.maven.org/maven2/org/jboss/aerogear/aerogear-android-security/3.0.0/
http://repo1.maven.org/maven2/org/jboss/aerogear/aerogear-android-store/3.0.0/
http://repo1.maven.org/maven2/org/jboss/aerogear/aerogear-android-auth/3.0.0/
http://repo1.maven.org/maven2/org/jboss/aerogear/aerogear-android-authz/3.0.0/

announcement etc. will follow, once UPS is released and we have updated the
docs.

-Matthias


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

> shipping....
>
> On Thu, May 12, 2016 at 10:45 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> Passes a quick smoke test.
>>
>> On Thu, May 12, 2016 at 4:40 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Thanks for tessting.
>>>
>>> I've deleted the broken pipe from teh 8215 repo, and have updated the
>>> version on a separate repo:
>>>
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8220/
>>>  (this includes only the fixed -pipe:3.0.0)
>>>
>>> -Matthias
>>>
>>> On Thu, May 12, 2016 at 10:11 PM, Summers Pittman <supittma at redhat.com>
>>> wrote:
>>>
>>>> I found one bug while testing.
>>>>
>>>> The pipe module uses reflection to build requests in a way that doesn't
>>>> always work with instant run (a great feature of Android Studio 2.0).
>>>> There is an open PR for this.
>>>>
>>>> https://github.com/aerogear/aerogear-android-pipe/pull/47
>>>>
>>>> On Wed, May 11, 2016 at 12:14 PM, Matthias Wessendorf <
>>>> matzew at apache.org> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> after some time, we got a new release staged, 3.0.0. Most relevant
>>>>> target is GCM-3 features, as long as InstanceID for GCM token regitration,
>>>>> as GCM.register is deprecated.
>>>>>
>>>>> Besides that there are some more changes in, e.g. an API change on our
>>>>> -store module.
>>>>>
>>>>> Full details are visible in JIRA:
>>>>> https://issues.jboss.org/projects/AGDROID/versions/12327585
>>>>>
>>>>> The staging repo is located here:
>>>>>
>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8215/
>>>>>
>>>>> Have fun testing it.
>>>>> -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
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>



-- 
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/20160513/8d829250/attachment.html 

From matzew at apache.org  Fri May 13 04:18:21 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 13 May 2016 10:18:21 +0200
Subject: [aerogear-dev] Travis CI failing for android-pipe
In-Reply-To: <CAAg5f2R9gO0Qxvq3jtz6uTcWA21CFytNeiFxCYdbMNTXaERVzA@mail.gmail.com>
References: <CAAg5f2R9gO0Qxvq3jtz6uTcWA21CFytNeiFxCYdbMNTXaERVzA@mail.gmail.com>
Message-ID: <CAAg5f2TCXTEjrP1=T3zN7hBD75_XXv=CyY3Qq+pF17A7T5NrLw@mail.gmail.com>

nevermind

On Fri, May 13, 2016 at 8:20 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> locally all works fine, otherwise the release plugin would not have
> allowed me to stage (and release) the bits.
>
> However, on Travis, I am getting a weird error from the
> 'com.simpligility.maven.plugins:android-maven-plugin' plugin:
>
>
> [INFO]
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building AeroGear Android Pipe Test 3.0.0
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- android-maven-plugin:4.4.1:instrument (default-cli) @
> aerogear-android-pipe-test ---
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 5.821 s
> [INFO] Finished at: 2016-05-13T06:15:22+00:00
> [INFO] Final Memory: 24M/491M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> com.simpligility.maven.plugins:android-maven-plugin:4.4.1:instrument
> (default-cli) on project aerogear-android-pipe-test: Execution default-cli
> of goal
> com.simpligility.maven.plugins:android-maven-plugin:4.4.1:instrument
> failed: java.io.FileNotFoundException:
> /home/travis/build/aerogear/aerogear-android-pipe/aerogear-android-pipe-test/target/AndroidManifest.xml
> (No such file or directory) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
>
>
>
>
> and yes, locally there is the
> 'aerogear-android-pipe/aerogear-android-pipe-test/target/AndroidManifest.xml'
> file in question.
>
> Any ideas  ?
>
>
>
>
> --
> 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/20160513/8c70de04/attachment.html 

From lholmqui at redhat.com  Fri May 13 09:10:38 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Fri, 13 May 2016 09:10:38 -0400
Subject: [aerogear-dev] Possible bug in getting windows variant with the
	REST API
Message-ID: <CALD3Fd0Du_5xk7QJiyxR4drN2O9KakdH+wBOAC1LfBbEV16tQQ@mail.gmail.com>

Currently using what is in master.


I've started to implement the GETing of variants for the node admin client
i posted earlier about and i think i might have run into a bug when trying
to get the Windows Variants.

here is a gist of what my current applications/variants looks like as JSON:
https://gist.github.com/lholmquist/44134f825373a5bce99624ac3d82c234

you will see i have 2 variants, one android and the other is a windows_wns
type.

using the endpoint "
http://locationofmyups/rest/applications/{PUSHAPPID}/{TYPE}" for android, i
get what i'm expecting,  but when i do the windows one, dont get anything
returned

i'm actually running my ups locally, so i'm able to set a break point, and
it does break in the windows GET code here
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/WindowsVariantEndpoint.java#L95

stepping through the getVariantsByType function,
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/AbstractVariantEndpoint.java#L135

i noticed that the "type" variable here is of "class
org.jboss.aerogear.unifiedpush.api.WindowsVariant"

and the variant.getClass() is actually
???org.jboss.aerogear.unifiedpush.api.WindowsWNSVariant

which is making the comparison fail and not return anything.

So is this a bug,  or do i need to pass something else in to make this
work,


note:  i've created all the applications and variants from the admin UI
screens
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160513/2c9aaa4c/attachment-0001.html 

From matzew at apache.org  Fri May 13 10:04:59 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 13 May 2016 16:04:59 +0200
Subject: [aerogear-dev] Possible bug in getting windows variant with the
 REST API
In-Reply-To: <CALD3Fd0Du_5xk7QJiyxR4drN2O9KakdH+wBOAC1LfBbEV16tQQ@mail.gmail.com>
References: <CALD3Fd0Du_5xk7QJiyxR4drN2O9KakdH+wBOAC1LfBbEV16tQQ@mail.gmail.com>
Message-ID: <CAAg5f2RvNbV4=dVVLQcpz5D_tQRs3PzNWqhrMmXLW2CeLrcqxg@mail.gmail.com>

variant type?

we have two different type for Windows (WP8 / 10) - use different push
(yes...)

https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/VariantType.java#L41-L49

On Fri, May 13, 2016 at 3:10 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> Currently using what is in master.
>
>
> I've started to implement the GETing of variants for the node admin client
> i posted earlier about and i think i might have run into a bug when trying
> to get the Windows Variants.
>
> here is a gist of what my current applications/variants looks like as
> JSON: https://gist.github.com/lholmquist/44134f825373a5bce99624ac3d82c234
>
> you will see i have 2 variants, one android and the other is a windows_wns
> type.
>
> using the endpoint "
> http://locationofmyups/rest/applications/{PUSHAPPID}/{TYPE}" for android,
> i get what i'm expecting,  but when i do the windows one, dont get anything
> returned
>
> i'm actually running my ups locally, so i'm able to set a break point, and
> it does break in the windows GET code here
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/WindowsVariantEndpoint.java#L95
>
> stepping through the getVariantsByType function,
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/AbstractVariantEndpoint.java#L135
>
> i noticed that the "type" variable here is of "class
> org.jboss.aerogear.unifiedpush.api.WindowsVariant"
>
> and the variant.getClass() is actually
> ???org.jboss.aerogear.unifiedpush.api.WindowsWNSVariant
>
> which is making the comparison fail and not return anything.
>
> So is this a bug,  or do i need to pass something else in to make this
> work,
>
>
> note:  i've created all the applications and variants from the admin UI
> screens
>
> _______________________________________________
> 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/20160513/2417ac52/attachment.html 

From lholmqui at redhat.com  Fri May 13 10:12:15 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Fri, 13 May 2016 10:12:15 -0400
Subject: [aerogear-dev] Possible bug in getting windows variant with the
 REST API
In-Reply-To: <CAAg5f2RvNbV4=dVVLQcpz5D_tQRs3PzNWqhrMmXLW2CeLrcqxg@mail.gmail.com>
References: <CALD3Fd0Du_5xk7QJiyxR4drN2O9KakdH+wBOAC1LfBbEV16tQQ@mail.gmail.com>
	<CAAg5f2RvNbV4=dVVLQcpz5D_tQRs3PzNWqhrMmXLW2CeLrcqxg@mail.gmail.com>
Message-ID: <CALD3Fd3qB+ai7KsoZXkECUnL2vAvpCVNDsxQMYBuz6w7EpW8+w@mail.gmail.com>

On Fri, May 13, 2016 at 10:04 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> variant type?
>
> we have two different type for Windows (WP8 / 10) - use different push
> (yes...)
>
>
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/VariantType.java#L41-L49
>

yup,  i know :)

so in this scenario my endpoint would then look like this:
http://locationofmyups/rest/applications/
5d77107a-3624-4456-a8fa-37036274ff61/windows_wns/
<http://locationofmyups/rest/applications/%7BPUSHAPPID%7D/%7BTYPE%7D>

which should return 1 variant, but it does not,
<http://locationofmyups/rest/applications/%7BPUSHAPPID%7D/%7BTYPE%7D>


>
>
> On Fri, May 13, 2016 at 3:10 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> Currently using what is in master.
>>
>>
>> I've started to implement the GETing of variants for the node admin
>> client i posted earlier about and i think i might have run into a bug when
>> trying to get the Windows Variants.
>>
>> here is a gist of what my current applications/variants looks like as
>> JSON: https://gist.github.com/lholmquist/44134f825373a5bce99624ac3d82c234
>>
>> you will see i have 2 variants, one android and the other is a
>> windows_wns type.
>>
>> using the endpoint "
>> http://locationofmyups/rest/applications/{PUSHAPPID}/{TYPE}" for
>> android, i get what i'm expecting,  but when i do the windows one, dont get
>> anything returned
>>
>> i'm actually running my ups locally, so i'm able to set a break point,
>> and it does break in the windows GET code here
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/WindowsVariantEndpoint.java#L95
>>
>> stepping through the getVariantsByType function,
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/AbstractVariantEndpoint.java#L135
>>
>> i noticed that the "type" variable here is of "class
>> org.jboss.aerogear.unifiedpush.api.WindowsVariant"
>>
>> and the variant.getClass() is actually
>> ???org.jboss.aerogear.unifiedpush.api.WindowsWNSVariant
>>
>> which is making the comparison fail and not return anything.
>>
>> So is this a bug,  or do i need to pass something else in to make this
>> work,
>>
>>
>> note:  i've created all the applications and variants from the admin UI
>> screens
>>
>> _______________________________________________
>> 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/20160513/aba0858b/attachment.html 

From matzew at apache.org  Fri May 13 10:15:10 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 13 May 2016 16:15:10 +0200
Subject: [aerogear-dev] Possible bug in getting windows variant with the
 REST API
In-Reply-To: <CALD3Fd3qB+ai7KsoZXkECUnL2vAvpCVNDsxQMYBuz6w7EpW8+w@mail.gmail.com>
References: <CALD3Fd0Du_5xk7QJiyxR4drN2O9KakdH+wBOAC1LfBbEV16tQQ@mail.gmail.com>
	<CAAg5f2RvNbV4=dVVLQcpz5D_tQRs3PzNWqhrMmXLW2CeLrcqxg@mail.gmail.com>
	<CALD3Fd3qB+ai7KsoZXkECUnL2vAvpCVNDsxQMYBuz6w7EpW8+w@mail.gmail.com>
Message-ID: <CAAg5f2R=bDaxM4sfOhpL5ymzrAn-tLo847QvB+_-nVGxwvbiuA@mail.gmail.com>

that... sounds like a bug ... no ?


On Fri, May 13, 2016 at 4:12 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

>
>
> On Fri, May 13, 2016 at 10:04 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> variant type?
>>
>> we have two different type for Windows (WP8 / 10) - use different push
>> (yes...)
>>
>>
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/VariantType.java#L41-L49
>>
>
> yup,  i know :)
>
> so in this scenario my endpoint would then look like this:
> http://locationofmyups/rest/applications/
> 5d77107a-3624-4456-a8fa-37036274ff61/windows_wns/
> <http://locationofmyups/rest/applications/%7BPUSHAPPID%7D/%7BTYPE%7D>
>
> which should return 1 variant, but it does not,
> <http://locationofmyups/rest/applications/%7BPUSHAPPID%7D/%7BTYPE%7D>
>
>
>>
>>
>> On Fri, May 13, 2016 at 3:10 PM, Luke Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>> Currently using what is in master.
>>>
>>>
>>> I've started to implement the GETing of variants for the node admin
>>> client i posted earlier about and i think i might have run into a bug when
>>> trying to get the Windows Variants.
>>>
>>> here is a gist of what my current applications/variants looks like as
>>> JSON:
>>> https://gist.github.com/lholmquist/44134f825373a5bce99624ac3d82c234
>>>
>>> you will see i have 2 variants, one android and the other is a
>>> windows_wns type.
>>>
>>> using the endpoint "
>>> http://locationofmyups/rest/applications/{PUSHAPPID}/{TYPE}" for
>>> android, i get what i'm expecting,  but when i do the windows one, dont get
>>> anything returned
>>>
>>> i'm actually running my ups locally, so i'm able to set a break point,
>>> and it does break in the windows GET code here
>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/WindowsVariantEndpoint.java#L95
>>>
>>> stepping through the getVariantsByType function,
>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/AbstractVariantEndpoint.java#L135
>>>
>>> i noticed that the "type" variable here is of "class
>>> org.jboss.aerogear.unifiedpush.api.WindowsVariant"
>>>
>>> and the variant.getClass() is actually
>>> ???org.jboss.aerogear.unifiedpush.api.WindowsWNSVariant
>>>
>>> which is making the comparison fail and not return anything.
>>>
>>> So is this a bug,  or do i need to pass something else in to make this
>>> work,
>>>
>>>
>>> note:  i've created all the applications and variants from the admin UI
>>> screens
>>>
>>> _______________________________________________
>>> 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/20160513/b13d3857/attachment-0001.html 

From lholmqui at redhat.com  Fri May 13 10:33:20 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Fri, 13 May 2016 10:33:20 -0400
Subject: [aerogear-dev] Possible bug in getting windows variant with the
 REST API
In-Reply-To: <CAAg5f2R=bDaxM4sfOhpL5ymzrAn-tLo847QvB+_-nVGxwvbiuA@mail.gmail.com>
References: <CALD3Fd0Du_5xk7QJiyxR4drN2O9KakdH+wBOAC1LfBbEV16tQQ@mail.gmail.com>
	<CAAg5f2RvNbV4=dVVLQcpz5D_tQRs3PzNWqhrMmXLW2CeLrcqxg@mail.gmail.com>
	<CALD3Fd3qB+ai7KsoZXkECUnL2vAvpCVNDsxQMYBuz6w7EpW8+w@mail.gmail.com>
	<CAAg5f2R=bDaxM4sfOhpL5ymzrAn-tLo847QvB+_-nVGxwvbiuA@mail.gmail.com>
Message-ID: <CALD3Fd3ZPAFQ1izSym4OWPoykMcWj7FKtBqoRQaqxXgkkMtF5Q@mail.gmail.com>

On Fri, May 13, 2016 at 10:15 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> that... sounds like a bug ... no ?
>
indeed

>
>
> On Fri, May 13, 2016 at 4:12 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>>
>>
>> On Fri, May 13, 2016 at 10:04 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> variant type?
>>>
>>> we have two different type for Windows (WP8 / 10) - use different push
>>> (yes...)
>>>
>>>
>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/VariantType.java#L41-L49
>>>
>>
>> yup,  i know :)
>>
>> so in this scenario my endpoint would then look like this:
>> http://locationofmyups/rest/applications/
>> 5d77107a-3624-4456-a8fa-37036274ff61/windows_wns/
>> <http://locationofmyups/rest/applications/%7BPUSHAPPID%7D/%7BTYPE%7D>
>>
>> which should return 1 variant, but it does not,
>> <http://locationofmyups/rest/applications/%7BPUSHAPPID%7D/%7BTYPE%7D>
>>
>>
>>>
>>>
>>> On Fri, May 13, 2016 at 3:10 PM, Luke Holmquist <lholmqui at redhat.com>
>>> wrote:
>>>
>>>> Currently using what is in master.
>>>>
>>>>
>>>> I've started to implement the GETing of variants for the node admin
>>>> client i posted earlier about and i think i might have run into a bug when
>>>> trying to get the Windows Variants.
>>>>
>>>> here is a gist of what my current applications/variants looks like as
>>>> JSON:
>>>> https://gist.github.com/lholmquist/44134f825373a5bce99624ac3d82c234
>>>>
>>>> you will see i have 2 variants, one android and the other is a
>>>> windows_wns type.
>>>>
>>>> using the endpoint "
>>>> http://locationofmyups/rest/applications/{PUSHAPPID}/{TYPE}" for
>>>> android, i get what i'm expecting,  but when i do the windows one, dont get
>>>> anything returned
>>>>
>>>> i'm actually running my ups locally, so i'm able to set a break point,
>>>> and it does break in the windows GET code here
>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/WindowsVariantEndpoint.java#L95
>>>>
>>>> stepping through the getVariantsByType function,
>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/AbstractVariantEndpoint.java#L135
>>>>
>>>> i noticed that the "type" variable here is of "class
>>>> org.jboss.aerogear.unifiedpush.api.WindowsVariant"
>>>>
>>>> and the variant.getClass() is actually
>>>> ???org.jboss.aerogear.unifiedpush.api.WindowsWNSVariant
>>>>
>>>> which is making the comparison fail and not return anything.
>>>>
>>>> So is this a bug,  or do i need to pass something else in to make this
>>>> work,
>>>>
>>>>
>>>> note:  i've created all the applications and variants from the admin UI
>>>> screens
>>>>
>>>> _______________________________________________
>>>> 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
>
> _______________________________________________
> 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/20160513/542df6f2/attachment.html 

From lholmqui at redhat.com  Fri May 13 10:44:32 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Fri, 13 May 2016 10:44:32 -0400
Subject: [aerogear-dev] Possible bug in getting windows variant with the
 REST API
In-Reply-To: <CALD3Fd3ZPAFQ1izSym4OWPoykMcWj7FKtBqoRQaqxXgkkMtF5Q@mail.gmail.com>
References: <CALD3Fd0Du_5xk7QJiyxR4drN2O9KakdH+wBOAC1LfBbEV16tQQ@mail.gmail.com>
	<CAAg5f2RvNbV4=dVVLQcpz5D_tQRs3PzNWqhrMmXLW2CeLrcqxg@mail.gmail.com>
	<CALD3Fd3qB+ai7KsoZXkECUnL2vAvpCVNDsxQMYBuz6w7EpW8+w@mail.gmail.com>
	<CAAg5f2R=bDaxM4sfOhpL5ymzrAn-tLo847QvB+_-nVGxwvbiuA@mail.gmail.com>
	<CALD3Fd3ZPAFQ1izSym4OWPoykMcWj7FKtBqoRQaqxXgkkMtF5Q@mail.gmail.com>
Message-ID: <CALD3Fd2NeELJVPzh7QL6-3siDLc=0y48V5RRFdBLD=bNTfWYXQ@mail.gmail.com>

created the JIRA:  https://issues.jboss.org/browse/AGPUSH-1631

On Fri, May 13, 2016 at 10:33 AM, Luke Holmquist <lholmqui at redhat.com>
wrote:

>
>
> On Fri, May 13, 2016 at 10:15 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> that... sounds like a bug ... no ?
>>
> indeed
>
>>
>>
>> On Fri, May 13, 2016 at 4:12 PM, Luke Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>>
>>>
>>> On Fri, May 13, 2016 at 10:04 AM, Matthias Wessendorf <matzew at apache.org
>>> > wrote:
>>>
>>>> variant type?
>>>>
>>>> we have two different type for Windows (WP8 / 10) - use different push
>>>> (yes...)
>>>>
>>>>
>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/model/api/src/main/java/org/jboss/aerogear/unifiedpush/api/VariantType.java#L41-L49
>>>>
>>>
>>> yup,  i know :)
>>>
>>> so in this scenario my endpoint would then look like this:
>>> http://locationofmyups/rest/applications/
>>> 5d77107a-3624-4456-a8fa-37036274ff61/windows_wns/
>>> <http://locationofmyups/rest/applications/%7BPUSHAPPID%7D/%7BTYPE%7D>
>>>
>>> which should return 1 variant, but it does not,
>>> <http://locationofmyups/rest/applications/%7BPUSHAPPID%7D/%7BTYPE%7D>
>>>
>>>
>>>>
>>>>
>>>> On Fri, May 13, 2016 at 3:10 PM, Luke Holmquist <lholmqui at redhat.com>
>>>> wrote:
>>>>
>>>>> Currently using what is in master.
>>>>>
>>>>>
>>>>> I've started to implement the GETing of variants for the node admin
>>>>> client i posted earlier about and i think i might have run into a bug when
>>>>> trying to get the Windows Variants.
>>>>>
>>>>> here is a gist of what my current applications/variants looks like as
>>>>> JSON:
>>>>> https://gist.github.com/lholmquist/44134f825373a5bce99624ac3d82c234
>>>>>
>>>>> you will see i have 2 variants, one android and the other is a
>>>>> windows_wns type.
>>>>>
>>>>> using the endpoint "
>>>>> http://locationofmyups/rest/applications/{PUSHAPPID}/{TYPE}" for
>>>>> android, i get what i'm expecting,  but when i do the windows one, dont get
>>>>> anything returned
>>>>>
>>>>> i'm actually running my ups locally, so i'm able to set a break point,
>>>>> and it does break in the windows GET code here
>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/WindowsVariantEndpoint.java#L95
>>>>>
>>>>> stepping through the getVariantsByType function,
>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/AbstractVariantEndpoint.java#L135
>>>>>
>>>>> i noticed that the "type" variable here is of "class
>>>>> org.jboss.aerogear.unifiedpush.api.WindowsVariant"
>>>>>
>>>>> and the variant.getClass() is actually
>>>>> ???org.jboss.aerogear.unifiedpush.api.WindowsWNSVariant
>>>>>
>>>>> which is making the comparison fail and not return anything.
>>>>>
>>>>> So is this a bug,  or do i need to pass something else in to make this
>>>>> work,
>>>>>
>>>>>
>>>>> note:  i've created all the applications and variants from the admin
>>>>> UI screens
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>
>> _______________________________________________
>> 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/20160513/c023245c/attachment-0001.html 

From supittma at redhat.com  Fri May 13 12:26:44 2016
From: supittma at redhat.com (Summers Pittman)
Date: Fri, 13 May 2016 12:26:44 -0400
Subject: [aerogear-dev] AGDroid-push 3.0.0 regression
Message-ID: <CAEQz2CsTgNzfN24W_4ghMkhnhs4Ua1gpjeRuvYem71VMb6BBdw@mail.gmail.com>

I found a small regression with the aerogear-android-push 3.0.0 module.

See : https://github.com/aerogear/aerogear-android-push/pull/61 and
AGDROID-541

Basically this means that applications which are killed by Android won't
handle push notifications correctly.

I suggest we restage and release the patch to maven central before we
"officially" release AGDroid 3.0.0.

Summers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160513/8426a921/attachment.html 

From supittma at redhat.com  Fri May 13 12:57:27 2016
From: supittma at redhat.com (Summers Pittman)
Date: Fri, 13 May 2016 12:57:27 -0400
Subject: [aerogear-dev] Unified Push, user-data field and Android push
Message-ID: <CAEQz2CtSuntnoh8LZ7s3wLz3zbs9D-Be1-wodqwg68zBXwtzPg@mail.gmail.com>

So I had a post on my Google+ (I know that was my reaction too) page from a
user who was having trouble with UPS, user-data, and Android.  I'm not sure
WHERE his problem is, but I will describe it here and we can discuss
further.

Let's say we send the following to UPS using the sender API :

{
     "message": {
"alert" : "Remote service failed. View FAQs.",
"sound": "default",
"badge": -1,
"user-data": {
"SXM": {
"CATEGORY" : "SERVICE",
"SERVICETYPE": "Remote",
"SRID": "BB4FC7F0-15E9-11E6-9F41-0050569C3256",
"APPCONTENT": "UNKNOWN",
"STATUS": "FAIL",
"STATUSCHANGE_DATETIME": "UNKNOWN",
"URL": "XYZABC.com"
}
}
     }
   }

Android will receive the following message bundle from Google :

Bundle[
  {aerogear-push-id=3f2b9477-fc9e-463a-94d7-d62bf55706e1,
   SXM={CATEGORY=SERVICE, SERVICETYPE=Remote,
SRID=BB4FC7F0-15E9-11E6-9F41-0050569C3256, APPCONTENT=UNKNOWN, STATUS=FAIL,
STATUSCHANGE_DATETIME=UNKNOWN, URL=XYZABC.com},
   alert=Remote service failed. View FAQs.,
   badge=-1,
   sound=default,
   collapse_key=do_not_collapse}
]

As we can see, several things have happened.  1) user-data has been rolled
up into a root element, and the SXM root object's JSON body has been
stripped of its jsonness.  IDEALLY we would be able to keep the body of
userdata as a string for user's to handle themselves.

I THINK this is an issue with how UPS converts the message for sending to
GCM, but i haven't researched that far.

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

From matzew at apache.org  Fri May 13 13:43:47 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 13 May 2016 19:43:47 +0200
Subject: [aerogear-dev] AGDroid-push 3.0.0 regression
In-Reply-To: <CAEQz2CsTgNzfN24W_4ghMkhnhs4Ua1gpjeRuvYem71VMb6BBdw@mail.gmail.com>
References: <CAEQz2CsTgNzfN24W_4ghMkhnhs4Ua1gpjeRuvYem71VMb6BBdw@mail.gmail.com>
Message-ID: <CAAg5f2T7q__Sxsrrowtm7v_Y0mRsY9mGGLNRPuyf_HoSi8d_LQ@mail.gmail.com>

3.0.1

the bits are on central

On Friday, 13 May 2016, Summers Pittman <supittma at redhat.com> wrote:

> I found a small regression with the aerogear-android-push 3.0.0 module.
>
> See : https://github.com/aerogear/aerogear-android-push/pull/61 and
> AGDROID-541
>
> Basically this means that applications which are killed by Android won't
> handle push notifications correctly.
>
> I suggest we restage and release the patch to maven central before we
> "officially" release AGDroid 3.0.0.
>
> Summers
>


-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160513/da82d959/attachment.html 

From matzew at apache.org  Fri May 13 23:03:30 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Sat, 14 May 2016 05:03:30 +0200
Subject: [aerogear-dev] Unified Push, user-data field and Android push
In-Reply-To: <CAEQz2CtSuntnoh8LZ7s3wLz3zbs9D-Be1-wodqwg68zBXwtzPg@mail.gmail.com>
References: <CAEQz2CtSuntnoh8LZ7s3wLz3zbs9D-Be1-wodqwg68zBXwtzPg@mail.gmail.com>
Message-ID: <CAAg5f2Q=_U2qowQwuiX31JuPuwOyNf4xq1KVQ8wenaX8ZcXVFA@mail.gmail.com>

yeah, here we do it:
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/GCMPushNotificationSender.java#L102-L107

On Fri, May 13, 2016 at 6:57 PM, Summers Pittman <supittma at redhat.com>
wrote:

> So I had a post on my Google+ (I know that was my reaction too) page from
> a user who was having trouble with UPS, user-data, and Android.  I'm not
> sure WHERE his problem is, but I will describe it here and we can discuss
> further.
>
> Let's say we send the following to UPS using the sender API :
>
> {
>      "message": {
> "alert" : "Remote service failed. View FAQs.",
> "sound": "default",
> "badge": -1,
> "user-data": {
> "SXM": {
> "CATEGORY" : "SERVICE",
> "SERVICETYPE": "Remote",
> "SRID": "BB4FC7F0-15E9-11E6-9F41-0050569C3256",
> "APPCONTENT": "UNKNOWN",
> "STATUS": "FAIL",
> "STATUSCHANGE_DATETIME": "UNKNOWN",
> "URL": "XYZABC.com"
> }
> }
>      }
>    }
>
> Android will receive the following message bundle from Google :
>
> Bundle[
>   {aerogear-push-id=3f2b9477-fc9e-463a-94d7-d62bf55706e1,
>    SXM={CATEGORY=SERVICE, SERVICETYPE=Remote,
> SRID=BB4FC7F0-15E9-11E6-9F41-0050569C3256, APPCONTENT=UNKNOWN, STATUS=FAIL,
> STATUSCHANGE_DATETIME=UNKNOWN, URL=XYZABC.com},
>    alert=Remote service failed. View FAQs.,
>    badge=-1,
>    sound=default,
>    collapse_key=do_not_collapse}
> ]
>
> As we can see, several things have happened.  1) user-data has been rolled
> up into a root element, and the SXM root object's JSON body has been
> stripped of its jsonness.  IDEALLY we would be able to keep the body of
> userdata as a string for user's to handle themselves.
>
> I THINK this is an issue with how UPS converts the message for sending to
> GCM, but i haven't researched that far.
>
> Summers
>
> _______________________________________________
> 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/20160514/9f129205/attachment.html 

From edewit at redhat.com  Sat May 14 04:22:10 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Sat, 14 May 2016 10:22:10 +0200
Subject: [aerogear-dev] Unified Push, user-data field and Android push
In-Reply-To: <CAAg5f2Q=_U2qowQwuiX31JuPuwOyNf4xq1KVQ8wenaX8ZcXVFA@mail.gmail.com>
References: <CAEQz2CtSuntnoh8LZ7s3wLz3zbs9D-Be1-wodqwg68zBXwtzPg@mail.gmail.com>
	<CAAg5f2Q=_U2qowQwuiX31JuPuwOyNf4xq1KVQ8wenaX8ZcXVFA@mail.gmail.com>
Message-ID: <CAO2B-fbukgFhthUY-XjPoT55T5wpbJ6t8rxKM30aB5j_63pXiA@mail.gmail.com>

Yeah, though he was doing something like that, basically we only support
key values in user-data not complex objects.

On Sat, May 14, 2016 at 5:03 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> yeah, here we do it:
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/GCMPushNotificationSender.java#L102-L107
>
> On Fri, May 13, 2016 at 6:57 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> So I had a post on my Google+ (I know that was my reaction too) page from
>> a user who was having trouble with UPS, user-data, and Android.  I'm not
>> sure WHERE his problem is, but I will describe it here and we can discuss
>> further.
>>
>> Let's say we send the following to UPS using the sender API :
>>
>> {
>>      "message": {
>> "alert" : "Remote service failed. View FAQs.",
>> "sound": "default",
>> "badge": -1,
>> "user-data": {
>> "SXM": {
>> "CATEGORY" : "SERVICE",
>> "SERVICETYPE": "Remote",
>> "SRID": "BB4FC7F0-15E9-11E6-9F41-0050569C3256",
>> "APPCONTENT": "UNKNOWN",
>> "STATUS": "FAIL",
>> "STATUSCHANGE_DATETIME": "UNKNOWN",
>> "URL": "XYZABC.com"
>> }
>> }
>>      }
>>    }
>>
>> Android will receive the following message bundle from Google :
>>
>> Bundle[
>>   {aerogear-push-id=3f2b9477-fc9e-463a-94d7-d62bf55706e1,
>>    SXM={CATEGORY=SERVICE, SERVICETYPE=Remote,
>> SRID=BB4FC7F0-15E9-11E6-9F41-0050569C3256, APPCONTENT=UNKNOWN, STATUS=FAIL,
>> STATUSCHANGE_DATETIME=UNKNOWN, URL=XYZABC.com},
>>    alert=Remote service failed. View FAQs.,
>>    badge=-1,
>>    sound=default,
>>    collapse_key=do_not_collapse}
>> ]
>>
>> As we can see, several things have happened.  1) user-data has been
>> rolled up into a root element, and the SXM root object's JSON body has been
>> stripped of its jsonness.  IDEALLY we would be able to keep the body of
>> userdata as a string for user's to handle themselves.
>>
>> I THINK this is an issue with how UPS converts the message for sending to
>> GCM, but i haven't researched that far.
>>
>> Summers
>>
>> _______________________________________________
>> 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
>



-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160514/3151202b/attachment-0001.html 

From matzew at apache.org  Sat May 14 07:22:46 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Sat, 14 May 2016 13:22:46 +0200
Subject: [aerogear-dev] aerogear-android-push 3.0.1 (was Re: AGDroid-push
 3.0.0 regression)
Message-ID: <CAAg5f2SQ_8CSXm-TCj=n2J+9jy3W0bAqDxWJ6UsC1yQcxTSc7Q@mail.gmail.com>

Hi,

I've staged a new version of the Android Push JAR:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8224/


It contains the fix for https://issues.jboss.org/browse/AGDROID-541

Let me know how it works for you, for a release early next week.

Thanks,
Matthias

On Fri, May 13, 2016 at 7:43 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> 3.0.1
>
> the bits are on central
>
>
> On Friday, 13 May 2016, Summers Pittman <supittma at redhat.com> wrote:
>
>> I found a small regression with the aerogear-android-push 3.0.0 module.
>>
>> See : https://github.com/aerogear/aerogear-android-push/pull/61 and
>> AGDROID-541
>>
>> Basically this means that applications which are killed by Android won't
>> handle push notifications correctly.
>>
>> I suggest we restage and release the patch to maven central before we
>> "officially" release AGDroid 3.0.0.
>>
>> Summers
>>
>
>
> --
> Sent from Gmail Mobile
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160514/8b977b13/attachment.html 

From supittma at redhat.com  Sat May 14 13:17:40 2016
From: supittma at redhat.com (Summers Pittman)
Date: Sat, 14 May 2016 13:17:40 -0400
Subject: [aerogear-dev] Unified Push, user-data field and Android push
In-Reply-To: <CAO2B-fbukgFhthUY-XjPoT55T5wpbJ6t8rxKM30aB5j_63pXiA@mail.gmail.com>
References: <CAEQz2CtSuntnoh8LZ7s3wLz3zbs9D-Be1-wodqwg68zBXwtzPg@mail.gmail.com>
	<CAAg5f2Q=_U2qowQwuiX31JuPuwOyNf4xq1KVQ8wenaX8ZcXVFA@mail.gmail.com>
	<CAO2B-fbukgFhthUY-XjPoT55T5wpbJ6t8rxKM30aB5j_63pXiA@mail.gmail.com>
Message-ID: <CAEQz2Cs-PFQUJJHLB3wu527N5ORw-FVnTG-qid-ynSP=1TEWUw@mail.gmail.com>

On Sat, May 14, 2016 at 4:22 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Yeah, though he was doing something like that, basically we only support
> key values in user-data not complex objects.
>

Perhaps we should just stringify complex objects?


> On Sat, May 14, 2016 at 5:03 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> yeah, here we do it:
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/GCMPushNotificationSender.java#L102-L107
>>
>> On Fri, May 13, 2016 at 6:57 PM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>> So I had a post on my Google+ (I know that was my reaction too) page
>>> from a user who was having trouble with UPS, user-data, and Android.  I'm
>>> not sure WHERE his problem is, but I will describe it here and we can
>>> discuss further.
>>>
>>> Let's say we send the following to UPS using the sender API :
>>>
>>> {
>>>      "message": {
>>> "alert" : "Remote service failed. View FAQs.",
>>> "sound": "default",
>>> "badge": -1,
>>> "user-data": {
>>> "SXM": {
>>> "CATEGORY" : "SERVICE",
>>> "SERVICETYPE": "Remote",
>>> "SRID": "BB4FC7F0-15E9-11E6-9F41-0050569C3256",
>>> "APPCONTENT": "UNKNOWN",
>>> "STATUS": "FAIL",
>>> "STATUSCHANGE_DATETIME": "UNKNOWN",
>>> "URL": "XYZABC.com"
>>> }
>>> }
>>>      }
>>>    }
>>>
>>> Android will receive the following message bundle from Google :
>>>
>>> Bundle[
>>>   {aerogear-push-id=3f2b9477-fc9e-463a-94d7-d62bf55706e1,
>>>    SXM={CATEGORY=SERVICE, SERVICETYPE=Remote,
>>> SRID=BB4FC7F0-15E9-11E6-9F41-0050569C3256, APPCONTENT=UNKNOWN, STATUS=FAIL,
>>> STATUSCHANGE_DATETIME=UNKNOWN, URL=XYZABC.com},
>>>    alert=Remote service failed. View FAQs.,
>>>    badge=-1,
>>>    sound=default,
>>>    collapse_key=do_not_collapse}
>>> ]
>>>
>>> As we can see, several things have happened.  1) user-data has been
>>> rolled up into a root element, and the SXM root object's JSON body has been
>>> stripped of its jsonness.  IDEALLY we would be able to keep the body of
>>> userdata as a string for user's to handle themselves.
>>>
>>> I THINK this is an issue with how UPS converts the message for sending
>>> to GCM, but i haven't researched that far.
>>>
>>> Summers
>>>
>>> _______________________________________________
>>> 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
>>
>
>
>
> --
> Cheers,
>        Erik Jan
>
> _______________________________________________
> 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/20160514/5c8cc3a8/attachment.html 

From supittma at redhat.com  Mon May 16 10:22:21 2016
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 16 May 2016 10:22:21 -0400
Subject: [aerogear-dev] AeroDec server help
Message-ID: <CAEQz2CvQuGbNCk2r-g8=NYERA9qESDJsEjbdxipA0s2C8wpqMQ@mail.gmail.com>

Hey guys,

I'm trying to update the aerodoc Android cookbook example, but I can't get
the AeroDoc backend server running.  Digging into the source it seems
pretty bitrotted (using picket link instead of keycloak, lucene doesn't
play nice with the wildfly docker image, dependencies are out of date, etc).

Who knows about it and can give me a hand some time?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160516/a09a88d8/attachment.html 

From matzew at apache.org  Mon May 16 12:47:52 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 16 May 2016 18:47:52 +0200
Subject: [aerogear-dev] AeroDec server help
In-Reply-To: <CAEQz2CvQuGbNCk2r-g8=NYERA9qESDJsEjbdxipA0s2C8wpqMQ@mail.gmail.com>
References: <CAEQz2CvQuGbNCk2r-g8=NYERA9qESDJsEjbdxipA0s2C8wpqMQ@mail.gmail.com>
Message-ID: <CAAg5f2QvtnmqYyz7qOSOei+ix2meuGOwc-cikwmFcpvwwh5ygA@mail.gmail.com>

On Mon, May 16, 2016 at 4:22 PM, Summers Pittman <supittma at redhat.com>
wrote:

> Hey guys,
>
> I'm trying to update the aerodoc Android cookbook example, but I can't get
> the AeroDoc backend server running.  Digging into the source it seems
> pretty bitrotted (using picket link instead of keycloak, lucene doesn't
> play nice with the wildfly docker image, dependencies are out of date, etc).
>

yes, that's a bit outdated, and we did try to get a GSoC student to be able
to work on that project, regarding updates. But didn't get enough slots.




>
> Who knows about it and can give me a hand some time?
>

I can take a look tomorrow, perhaps at some point we should schedule some
time to do an overhaul ourselves.



>
> _______________________________________________
> 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/20160516/144ad5ca/attachment.html 

From supittma at redhat.com  Mon May 16 13:04:11 2016
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 16 May 2016 13:04:11 -0400
Subject: [aerogear-dev] AeroDec server help
In-Reply-To: <CAAg5f2QvtnmqYyz7qOSOei+ix2meuGOwc-cikwmFcpvwwh5ygA@mail.gmail.com>
References: <CAEQz2CvQuGbNCk2r-g8=NYERA9qESDJsEjbdxipA0s2C8wpqMQ@mail.gmail.com>
	<CAAg5f2QvtnmqYyz7qOSOei+ix2meuGOwc-cikwmFcpvwwh5ygA@mail.gmail.com>
Message-ID: <CAEQz2CsN=m5_Edo0Fy=wyQff9ZKqfdeuCd8YjVzgou7AAU8JQw@mail.gmail.com>

Good news, I got it working.  Looks like Docker had some weird permissions
under the hood for lucene.  I also had to edit the pom to get dom4j loading
correctly.

On Mon, May 16, 2016 at 12:47 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Mon, May 16, 2016 at 4:22 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> Hey guys,
>>
>> I'm trying to update the aerodoc Android cookbook example, but I can't
>> get the AeroDoc backend server running.  Digging into the source it seems
>> pretty bitrotted (using picket link instead of keycloak, lucene doesn't
>> play nice with the wildfly docker image, dependencies are out of date, etc).
>>
>
> yes, that's a bit outdated, and we did try to get a GSoC student to be
> able to work on that project, regarding updates. But didn't get enough
> slots.
>
>
>
>
>>
>> Who knows about it and can give me a hand some time?
>>
>
> I can take a look tomorrow, perhaps at some point we should schedule some
> time to do an overhaul ourselves.
>
>
>
>>
>> _______________________________________________
>> 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/20160516/da30373f/attachment-0001.html 

From matzew at apache.org  Mon May 16 13:39:58 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 16 May 2016 19:39:58 +0200
Subject: [aerogear-dev] AeroDec server help
In-Reply-To: <CAEQz2CsN=m5_Edo0Fy=wyQff9ZKqfdeuCd8YjVzgou7AAU8JQw@mail.gmail.com>
References: <CAEQz2CvQuGbNCk2r-g8=NYERA9qESDJsEjbdxipA0s2C8wpqMQ@mail.gmail.com>
	<CAAg5f2QvtnmqYyz7qOSOei+ix2meuGOwc-cikwmFcpvwwh5ygA@mail.gmail.com>
	<CAEQz2CsN=m5_Edo0Fy=wyQff9ZKqfdeuCd8YjVzgou7AAU8JQw@mail.gmail.com>
Message-ID: <CAAg5f2Qc0GX3ApRzOkuP-8kbHeFFun7iecf+jVC5+NC-7JP51Q@mail.gmail.com>

cool! Mind sending a PR for the 'containerization' of the backend?

On Mon, May 16, 2016 at 7:04 PM, Summers Pittman <supittma at redhat.com>
wrote:

> Good news, I got it working.  Looks like Docker had some weird permissions
> under the hood for lucene.  I also had to edit the pom to get dom4j loading
> correctly.
>
> On Mon, May 16, 2016 at 12:47 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Mon, May 16, 2016 at 4:22 PM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>> Hey guys,
>>>
>>> I'm trying to update the aerodoc Android cookbook example, but I can't
>>> get the AeroDoc backend server running.  Digging into the source it seems
>>> pretty bitrotted (using picket link instead of keycloak, lucene doesn't
>>> play nice with the wildfly docker image, dependencies are out of date, etc).
>>>
>>
>> yes, that's a bit outdated, and we did try to get a GSoC student to be
>> able to work on that project, regarding updates. But didn't get enough
>> slots.
>>
>>
>>
>>
>>>
>>> Who knows about it and can give me a hand some time?
>>>
>>
>> I can take a look tomorrow, perhaps at some point we should schedule some
>> time to do an overhaul ourselves.
>>
>>
>>
>>>
>>> _______________________________________________
>>> 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/20160516/e17a715c/attachment.html 

From supittma at redhat.com  Mon May 16 13:54:23 2016
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 16 May 2016 13:54:23 -0400
Subject: [aerogear-dev] AeroDec server help
In-Reply-To: <CAAg5f2Qc0GX3ApRzOkuP-8kbHeFFun7iecf+jVC5+NC-7JP51Q@mail.gmail.com>
References: <CAEQz2CvQuGbNCk2r-g8=NYERA9qESDJsEjbdxipA0s2C8wpqMQ@mail.gmail.com>
	<CAAg5f2QvtnmqYyz7qOSOei+ix2meuGOwc-cikwmFcpvwwh5ygA@mail.gmail.com>
	<CAEQz2CsN=m5_Edo0Fy=wyQff9ZKqfdeuCd8YjVzgou7AAU8JQw@mail.gmail.com>
	<CAAg5f2Qc0GX3ApRzOkuP-8kbHeFFun7iecf+jVC5+NC-7JP51Q@mail.gmail.com>
Message-ID: <CAEQz2CtnWUN2YuxAAqptT8uvE42r7nYoLV4XhuZA1SFYFPAR-g@mail.gmail.com>

OH, I never got it running in Docker.

On Mon, May 16, 2016 at 1:39 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> cool! Mind sending a PR for the 'containerization' of the backend?
>
> On Mon, May 16, 2016 at 7:04 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> Good news, I got it working.  Looks like Docker had some weird
>> permissions under the hood for lucene.  I also had to edit the pom to get
>> dom4j loading correctly.
>>
>> On Mon, May 16, 2016 at 12:47 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>>
>>>
>>> On Mon, May 16, 2016 at 4:22 PM, Summers Pittman <supittma at redhat.com>
>>> wrote:
>>>
>>>> Hey guys,
>>>>
>>>> I'm trying to update the aerodoc Android cookbook example, but I can't
>>>> get the AeroDoc backend server running.  Digging into the source it seems
>>>> pretty bitrotted (using picket link instead of keycloak, lucene doesn't
>>>> play nice with the wildfly docker image, dependencies are out of date, etc).
>>>>
>>>
>>> yes, that's a bit outdated, and we did try to get a GSoC student to be
>>> able to work on that project, regarding updates. But didn't get enough
>>> slots.
>>>
>>>
>>>
>>>
>>>>
>>>> Who knows about it and can give me a hand some time?
>>>>
>>>
>>> I can take a look tomorrow, perhaps at some point we should schedule
>>> some time to do an overhaul ourselves.
>>>
>>>
>>>
>>>>
>>>> _______________________________________________
>>>> 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
>
> _______________________________________________
> 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/20160516/95d524bc/attachment.html 

From supittma at redhat.com  Mon May 16 14:21:33 2016
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 16 May 2016 14:21:33 -0400
Subject: [aerogear-dev] aerogear-android-push 3.0.1 (was Re:
 AGDroid-push 3.0.0 regression)
In-Reply-To: <CAAg5f2SQ_8CSXm-TCj=n2J+9jy3W0bAqDxWJ6UsC1yQcxTSc7Q@mail.gmail.com>
References: <CAAg5f2SQ_8CSXm-TCj=n2J+9jy3W0bAqDxWJ6UsC1yQcxTSc7Q@mail.gmail.com>
Message-ID: <CAEQz2Cuj0RahXBRa=mbLw1twU1gQxyXUQ3XDvxocT1CJtgYBuA@mail.gmail.com>

On Sat, May 14, 2016 at 7:22 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> I've staged a new version of the Android Push JAR:
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8224/
>
>
> It contains the fix for https://issues.jboss.org/browse/AGDROID-541
>
> Let me know how it works for you, for a release early next week.
>
> THings are working on my end now.

> Thanks,
> Matthias
>
> On Fri, May 13, 2016 at 7:43 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> 3.0.1
>>
>> the bits are on central
>>
>>
>> On Friday, 13 May 2016, Summers Pittman <supittma at redhat.com> wrote:
>>
>>> I found a small regression with the aerogear-android-push 3.0.0 module.
>>>
>>> See : https://github.com/aerogear/aerogear-android-push/pull/61 and
>>> AGDROID-541
>>>
>>> Basically this means that applications which are killed by Android won't
>>> handle push notifications correctly.
>>>
>>> I suggest we restage and release the patch to maven central before we
>>> "officially" release AGDroid 3.0.0.
>>>
>>> Summers
>>>
>>
>>
>> --
>> Sent from Gmail Mobile
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160516/6463f3b0/attachment-0001.html 

From supittma at redhat.com  Mon May 16 14:21:50 2016
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 16 May 2016 14:21:50 -0400
Subject: [aerogear-dev] Staging of UPS 1.1.3.Final
In-Reply-To: <CAAg5f2Sn3SXPoTn572yM0Fg+jWZfN9BFRDA9QEqdpcgtn2kOfA@mail.gmail.com>
References: <CAAg5f2R1e3F+KoXwRmYs=za3=YVdkoJdgL9f3xaMs8hqKa_fPg@mail.gmail.com>
	<CAAg5f2Sn3SXPoTn572yM0Fg+jWZfN9BFRDA9QEqdpcgtn2kOfA@mail.gmail.com>
Message-ID: <CAEQz2Ct677eua=jqSw3hhCaOKKZKsGjea=C-n8DRAu2VhMMe+Q@mail.gmail.com>

Works for me

On Wed, May 11, 2016 at 2:56 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> The 1.1.x dockerfiles are now also updated:
> https://github.com/aerogear/dockerfiles/pull/17
>
> On Wed, May 11, 2016 at 8:48 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hello there!
>>
>> for the 1.1.x series we are releasing 1.1.3.Final.
>>
>> Biggest focus for this release was GCM-3 APIs for Android push. A full
>> list of all changes is listed here:
>> https://issues.jboss.org/projects/AGPUSH/versions/12330260
>>
>> You can find the staging repository here:
>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8216/
>>
>> A pre-release is available on github as well:
>>
>> https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.1.3.Final
>>
>> Please give it a try over the next few days, so that we can release it!
>>
>> Thanks,
>> Matthias
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> 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/20160516/71b10d9a/attachment-0001.html 

From idel.pivnitskiy at gmail.com  Tue May 17 11:33:59 2016
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Tue, 17 May 2016 18:33:59 +0300
Subject: [aerogear-dev] GSoC plan for WebPush
Message-ID: <CAN+BUJpj+Nd_E67un6dm2xzZO6dNf5YvH7xiQmuMZX4iaMonSQ@mail.gmail.com>

Hi all,

I've come back from the little vocation and ready for the work on my GSoC
project.

What will be our plan?
I may work according to my proposal: the first steps will be the adding
WebPush support for Chrome and Firefox directly to UPS (through Google
Cloud Messaging and Mozilla Push Service).
Another way: I may begin my work from WebPush Server.

If we will begin from UPS, from which branch should I work? And for which
release?

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/20160517/013c5f43/attachment.html 

From matzew at apache.org  Tue May 17 11:38:47 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 17 May 2016 17:38:47 +0200
Subject: [aerogear-dev] GSoC plan for WebPush
In-Reply-To: <CAN+BUJpj+Nd_E67un6dm2xzZO6dNf5YvH7xiQmuMZX4iaMonSQ@mail.gmail.com>
References: <CAN+BUJpj+Nd_E67un6dm2xzZO6dNf5YvH7xiQmuMZX4iaMonSQ@mail.gmail.com>
Message-ID: <CAAg5f2Rg=zjVzxJtGOUBMx6rsbyLQ9q3yeee+J1tNp6ZPFQrVw@mail.gmail.com>

Hi,



On Tue, May 17, 2016 at 5:33 PM, Idel Pivnitskiy <idel.pivnitskiy at gmail.com>
wrote:

> Hi all,
>
> I've come back from the little vocation and ready for the work on my GSoC
> project.
>
> What will be our plan?
> I may work according to my proposal: the first steps will be the adding
> WebPush support for Chrome and Firefox directly to UPS (through Google
> Cloud Messaging and Mozilla Push Service).
>

I like that, but


> Another way: I may begin my work from WebPush Server.
>

Does it make sense starting with more focused examples? Showing
Chrome/Firefox receiving message via the WebPush APIs from the standalone
WebPush Server ?


At the end of the day, UPS is just another 'driver', triggering the push ?


Oh, I think we can also remove the SimplePush from the master branch of
UPS, while on this project, no ?



>
> If we will begin from UPS, from which branch should I work? And for which
> release?
>
> 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/20160517/2cde148d/attachment.html 

From idel.pivnitskiy at gmail.com  Tue May 17 12:03:28 2016
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Tue, 17 May 2016 19:03:28 +0300
Subject: [aerogear-dev] GSoC plan for WebPush
In-Reply-To: <CAAg5f2Rg=zjVzxJtGOUBMx6rsbyLQ9q3yeee+J1tNp6ZPFQrVw@mail.gmail.com>
References: <CAN+BUJpj+Nd_E67un6dm2xzZO6dNf5YvH7xiQmuMZX4iaMonSQ@mail.gmail.com>
	<CAAg5f2Rg=zjVzxJtGOUBMx6rsbyLQ9q3yeee+J1tNp6ZPFQrVw@mail.gmail.com>
Message-ID: <CAN+BUJpaHq1cpQq6v5-aZPmTKqO6Zv-ULOi+uYY+bw+d9MKWig@mail.gmail.com>

>
> Does it make sense starting with more focused examples? Showing
> Chrome/Firefox receiving message via the WebPush APIs from the standalone
> WebPush Server ?


I think that we don't need our WebPush Server for Chrome/Firefox support.
Because it possible to send push messages to Chrome only through GCM, using
their API-key.


> I think we can also remove the SimplePush from the master branch of UPS,
> while on this project, no ?


Think that it could be done at the end of the summer, if there are no
reasons to keep it. After or during the integration of WebPush Server to
UPS. I prefer after, like it was with Doclet and Miredot.



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

On Tue, May 17, 2016 at 6:38 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
>
>
> On Tue, May 17, 2016 at 5:33 PM, Idel Pivnitskiy <
> idel.pivnitskiy at gmail.com> wrote:
>
>> Hi all,
>>
>> I've come back from the little vocation and ready for the work on my GSoC
>> project.
>>
>> What will be our plan?
>> I may work according to my proposal: the first steps will be the adding
>> WebPush support for Chrome and Firefox directly to UPS (through Google
>> Cloud Messaging and Mozilla Push Service).
>>
>
> I like that, but
>
>
>> Another way: I may begin my work from WebPush Server.
>>
>
> Does it make sense starting with more focused examples? Showing
> Chrome/Firefox receiving message via the WebPush APIs from the standalone
> WebPush Server ?
>
>
> At the end of the day, UPS is just another 'driver', triggering the push ?
>
>
> Oh, I think we can also remove the SimplePush from the master branch of
> UPS, while on this project, no ?
>
>
>
>>
>> If we will begin from UPS, from which branch should I work? And for which
>> release?
>>
>> 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
>
> _______________________________________________
> 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/20160517/963bc985/attachment.html 

From matzew at apache.org  Tue May 17 12:45:03 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 17 May 2016 18:45:03 +0200
Subject: [aerogear-dev] GSoC plan for WebPush
In-Reply-To: <CAN+BUJpaHq1cpQq6v5-aZPmTKqO6Zv-ULOi+uYY+bw+d9MKWig@mail.gmail.com>
References: <CAN+BUJpj+Nd_E67un6dm2xzZO6dNf5YvH7xiQmuMZX4iaMonSQ@mail.gmail.com>
	<CAAg5f2Rg=zjVzxJtGOUBMx6rsbyLQ9q3yeee+J1tNp6ZPFQrVw@mail.gmail.com>
	<CAN+BUJpaHq1cpQq6v5-aZPmTKqO6Zv-ULOi+uYY+bw+d9MKWig@mail.gmail.com>
Message-ID: <CAAg5f2TMpu4fZN16-a3UmFRq53S0JPsoiW46TSzRxarqbsNRYw@mail.gmail.com>

On Tue, May 17, 2016 at 6:03 PM, Idel Pivnitskiy <idel.pivnitskiy at gmail.com>
wrote:

> Does it make sense starting with more focused examples? Showing
>> Chrome/Firefox receiving message via the WebPush APIs from the standalone
>> WebPush Server ?
>
>
> I think that we don't need our WebPush Server for Chrome/Firefox support.
> Because it possible to send push messages to Chrome only through GCM,
> using their API-key.
>

Right, but that goes through their service. I think one of the big
advantages here is that with a truly open WebPush Server/Protocol/API, you
as a company, can run your own, inpendent push network. Having support to
connect to a custom WebPush server from the (standard?) JS API would be
nice. Makes you more independent.

E.g. imagine push on a private network, where not all devcies are connected
to the public internet ;-)

Not a high priority, but IMO worth to think about this


>
>
>> I think we can also remove the SimplePush from the master branch of UPS,
>> while on this project, no ?
>
>
> Think that it could be done at the end of the summer, if there are no
> reasons to keep it. After or during the integration of WebPush Server to
> UPS. I prefer after, like it was with Doclet and Miredot.
>

+1 makes sense to remove SimplePush, once WebPush is around. WebPush is the
successor of SimplePush in general

>
>
>
> Best regards,
> Idel Pivnitskiy
> --
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>
> On Tue, May 17, 2016 at 6:38 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>>
>>
>> On Tue, May 17, 2016 at 5:33 PM, Idel Pivnitskiy <
>> idel.pivnitskiy at gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> I've come back from the little vocation and ready for the work on my
>>> GSoC project.
>>>
>>> What will be our plan?
>>> I may work according to my proposal: the first steps will be the adding
>>> WebPush support for Chrome and Firefox directly to UPS (through Google
>>> Cloud Messaging and Mozilla Push Service).
>>>
>>
>> I like that, but
>>
>>
>>> Another way: I may begin my work from WebPush Server.
>>>
>>
>> Does it make sense starting with more focused examples? Showing
>> Chrome/Firefox receiving message via the WebPush APIs from the standalone
>> WebPush Server ?
>>
>>
>> At the end of the day, UPS is just another 'driver', triggering the push ?
>>
>>
>> Oh, I think we can also remove the SimplePush from the master branch of
>> UPS, while on this project, no ?
>>
>>
>>
>>>
>>> If we will begin from UPS, from which branch should I work? And for
>>> which release?
>>>
>>> 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
>>
>> _______________________________________________
>> 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/20160517/dd825661/attachment-0001.html 

From idel.pivnitskiy at gmail.com  Tue May 17 13:03:53 2016
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Tue, 17 May 2016 20:03:53 +0300
Subject: [aerogear-dev] GSoC plan for WebPush
In-Reply-To: <CAAg5f2TMpu4fZN16-a3UmFRq53S0JPsoiW46TSzRxarqbsNRYw@mail.gmail.com>
References: <CAN+BUJpj+Nd_E67un6dm2xzZO6dNf5YvH7xiQmuMZX4iaMonSQ@mail.gmail.com>
	<CAAg5f2Rg=zjVzxJtGOUBMx6rsbyLQ9q3yeee+J1tNp6ZPFQrVw@mail.gmail.com>
	<CAN+BUJpaHq1cpQq6v5-aZPmTKqO6Zv-ULOi+uYY+bw+d9MKWig@mail.gmail.com>
	<CAAg5f2TMpu4fZN16-a3UmFRq53S0JPsoiW46TSzRxarqbsNRYw@mail.gmail.com>
Message-ID: <CAN+BUJqWBwWV947bW+QrJizDiMo_WjbuMH6KoNOSud-gqUtV0w@mail.gmail.com>

>
> Right, but that goes through their service. I think one of the big
> advantages here is that with a truly open WebPush Server/Protocol/API, you
> as a company, can run your own, inpendent push network. Having support to
> connect to a custom WebPush server from the (standard?) JS API would be
> nice. Makes you more independent.
> E.g. imagine push on a private network, where not all devcies are
> connected to the public internet ;-)


Yes, good case!
But I think that it will not work with Chrome now:
https://developer.mozilla.org/en-US/docs/Web/API/Push_API/Using_the_Push_API#Extra_steps_for_Chrome_support
Hope that it will be possible with Firefox, but I need to double check it.

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

On Tue, May 17, 2016 at 7:45 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Tue, May 17, 2016 at 6:03 PM, Idel Pivnitskiy <
> idel.pivnitskiy at gmail.com> wrote:
>
>> Does it make sense starting with more focused examples? Showing
>>> Chrome/Firefox receiving message via the WebPush APIs from the standalone
>>> WebPush Server ?
>>
>>
>> I think that we don't need our WebPush Server for Chrome/Firefox support.
>> Because it possible to send push messages to Chrome only through GCM,
>> using their API-key.
>>
>
> Right, but that goes through their service. I think one of the big
> advantages here is that with a truly open WebPush Server/Protocol/API, you
> as a company, can run your own, inpendent push network. Having support to
> connect to a custom WebPush server from the (standard?) JS API would be
> nice. Makes you more independent.
>
> E.g. imagine push on a private network, where not all devcies are
> connected to the public internet ;-)
>
> Not a high priority, but IMO worth to think about this
>
>
>>
>>
>>> I think we can also remove the SimplePush from the master branch of UPS,
>>> while on this project, no ?
>>
>>
>> Think that it could be done at the end of the summer, if there are no
>> reasons to keep it. After or during the integration of WebPush Server to
>> UPS. I prefer after, like it was with Doclet and Miredot.
>>
>
> +1 makes sense to remove SimplePush, once WebPush is around. WebPush is
> the successor of SimplePush in general
>
>>
>>
>>
>> Best regards,
>> Idel Pivnitskiy
>> --
>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>>
>> On Tue, May 17, 2016 at 6:38 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>>
>>>
>>> On Tue, May 17, 2016 at 5:33 PM, Idel Pivnitskiy <
>>> idel.pivnitskiy at gmail.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I've come back from the little vocation and ready for the work on my
>>>> GSoC project.
>>>>
>>>> What will be our plan?
>>>> I may work according to my proposal: the first steps will be the adding
>>>> WebPush support for Chrome and Firefox directly to UPS (through Google
>>>> Cloud Messaging and Mozilla Push Service).
>>>>
>>>
>>> I like that, but
>>>
>>>
>>>> Another way: I may begin my work from WebPush Server.
>>>>
>>>
>>> Does it make sense starting with more focused examples? Showing
>>> Chrome/Firefox receiving message via the WebPush APIs from the standalone
>>> WebPush Server ?
>>>
>>>
>>> At the end of the day, UPS is just another 'driver', triggering the push
>>> ?
>>>
>>>
>>> Oh, I think we can also remove the SimplePush from the master branch of
>>> UPS, while on this project, no ?
>>>
>>>
>>>
>>>>
>>>> If we will begin from UPS, from which branch should I work? And for
>>>> which release?
>>>>
>>>> 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
>>>
>>> _______________________________________________
>>> 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/20160517/dcb33db2/attachment.html 

From matzew at apache.org  Tue May 17 14:29:35 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 17 May 2016 20:29:35 +0200
Subject: [aerogear-dev] GSoC plan for WebPush
In-Reply-To: <CAN+BUJqWBwWV947bW+QrJizDiMo_WjbuMH6KoNOSud-gqUtV0w@mail.gmail.com>
References: <CAN+BUJpj+Nd_E67un6dm2xzZO6dNf5YvH7xiQmuMZX4iaMonSQ@mail.gmail.com>
	<CAAg5f2Rg=zjVzxJtGOUBMx6rsbyLQ9q3yeee+J1tNp6ZPFQrVw@mail.gmail.com>
	<CAN+BUJpaHq1cpQq6v5-aZPmTKqO6Zv-ULOi+uYY+bw+d9MKWig@mail.gmail.com>
	<CAAg5f2TMpu4fZN16-a3UmFRq53S0JPsoiW46TSzRxarqbsNRYw@mail.gmail.com>
	<CAN+BUJqWBwWV947bW+QrJizDiMo_WjbuMH6KoNOSud-gqUtV0w@mail.gmail.com>
Message-ID: <CAAg5f2QSi_Q1mk5cHRjL4W9gmk4vUF-N_6GOVEQncyUA8_aE8g@mail.gmail.com>

On Tue, May 17, 2016 at 7:03 PM, Idel Pivnitskiy <idel.pivnitskiy at gmail.com>
wrote:

> Right, but that goes through their service. I think one of the big
>> advantages here is that with a truly open WebPush Server/Protocol/API, you
>> as a company, can run your own, inpendent push network. Having support to
>> connect to a custom WebPush server from the (standard?) JS API would be
>> nice. Makes you more independent.
>> E.g. imagine push on a private network, where not all devcies are
>> connected to the public internet ;-)
>
>
> Yes, good case!
> But I think that it will not work with Chrome now:
> https://developer.mozilla.org/en-US/docs/Web/API/Push_API/Using_the_Push_API#Extra_steps_for_Chrome_support
> Hope that it will be possible with Firefox, but I need to double check it.
>

We could offer a little decorator, if the user explicitly wants a customer
server :)

We did that for simple push too:
https://github.com/aerogear/aerogear-js/blob/master/src/simplepush/aerogear.simplepush.js#L27



>
> Best regards,
> Idel Pivnitskiy
> --
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>
> On Tue, May 17, 2016 at 7:45 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Tue, May 17, 2016 at 6:03 PM, Idel Pivnitskiy <
>> idel.pivnitskiy at gmail.com> wrote:
>>
>>> Does it make sense starting with more focused examples? Showing
>>>> Chrome/Firefox receiving message via the WebPush APIs from the standalone
>>>> WebPush Server ?
>>>
>>>
>>> I think that we don't need our WebPush Server for Chrome/Firefox
>>> support. Because it possible to send push messages to Chrome only
>>> through GCM, using their API-key.
>>>
>>
>> Right, but that goes through their service. I think one of the big
>> advantages here is that with a truly open WebPush Server/Protocol/API, you
>> as a company, can run your own, inpendent push network. Having support to
>> connect to a custom WebPush server from the (standard?) JS API would be
>> nice. Makes you more independent.
>>
>> E.g. imagine push on a private network, where not all devcies are
>> connected to the public internet ;-)
>>
>> Not a high priority, but IMO worth to think about this
>>
>>
>>>
>>>
>>>> I think we can also remove the SimplePush from the master branch of
>>>> UPS, while on this project, no ?
>>>
>>>
>>> Think that it could be done at the end of the summer, if there are no
>>> reasons to keep it. After or during the integration of WebPush Server to
>>> UPS. I prefer after, like it was with Doclet and Miredot.
>>>
>>
>> +1 makes sense to remove SimplePush, once WebPush is around. WebPush is
>> the successor of SimplePush in general
>>
>>>
>>>
>>>
>>> Best regards,
>>> Idel Pivnitskiy
>>> --
>>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>>> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>>>
>>> On Tue, May 17, 2016 at 6:38 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>>
>>>>
>>>> On Tue, May 17, 2016 at 5:33 PM, Idel Pivnitskiy <
>>>> idel.pivnitskiy at gmail.com> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I've come back from the little vocation and ready for the work on my
>>>>> GSoC project.
>>>>>
>>>>> What will be our plan?
>>>>> I may work according to my proposal: the first steps will be the
>>>>> adding WebPush support for Chrome and Firefox directly to UPS (through
>>>>> Google Cloud Messaging and Mozilla Push Service).
>>>>>
>>>>
>>>> I like that, but
>>>>
>>>>
>>>>> Another way: I may begin my work from WebPush Server.
>>>>>
>>>>
>>>> Does it make sense starting with more focused examples? Showing
>>>> Chrome/Firefox receiving message via the WebPush APIs from the standalone
>>>> WebPush Server ?
>>>>
>>>>
>>>> At the end of the day, UPS is just another 'driver', triggering the
>>>> push ?
>>>>
>>>>
>>>> Oh, I think we can also remove the SimplePush from the master branch of
>>>> UPS, while on this project, no ?
>>>>
>>>>
>>>>
>>>>>
>>>>> If we will begin from UPS, from which branch should I work? And for
>>>>> which release?
>>>>>
>>>>> 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
>>>>
>>>> _______________________________________________
>>>> 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/20160517/ddbfc06f/attachment-0001.html 

From idel.pivnitskiy at gmail.com  Wed May 18 06:48:45 2016
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Wed, 18 May 2016 13:48:45 +0300
Subject: [aerogear-dev] GSoC plan for WebPush
In-Reply-To: <CAAg5f2QSi_Q1mk5cHRjL4W9gmk4vUF-N_6GOVEQncyUA8_aE8g@mail.gmail.com>
References: <CAN+BUJpj+Nd_E67un6dm2xzZO6dNf5YvH7xiQmuMZX4iaMonSQ@mail.gmail.com>
	<CAAg5f2Rg=zjVzxJtGOUBMx6rsbyLQ9q3yeee+J1tNp6ZPFQrVw@mail.gmail.com>
	<CAN+BUJpaHq1cpQq6v5-aZPmTKqO6Zv-ULOi+uYY+bw+d9MKWig@mail.gmail.com>
	<CAAg5f2TMpu4fZN16-a3UmFRq53S0JPsoiW46TSzRxarqbsNRYw@mail.gmail.com>
	<CAN+BUJqWBwWV947bW+QrJizDiMo_WjbuMH6KoNOSud-gqUtV0w@mail.gmail.com>
	<CAAg5f2QSi_Q1mk5cHRjL4W9gmk4vUF-N_6GOVEQncyUA8_aE8g@mail.gmail.com>
Message-ID: <CAN+BUJpDK3cgPFJuS2E7UavyLuN_F1LQ9ShFwTZ-fKeNRU9EvQ@mail.gmail.com>

>
> Right, but that goes through their service. I think one of the big
>>> advantages here is that with a truly open WebPush Server/Protocol/API, you
>>> as a company, can run your own, inpendent push network. Having support to
>>> connect to a custom WebPush server from the (standard?) JS API would be
>>> nice. Makes you more independent.
>>> E.g. imagine push on a private network, where not all devcies are
>>> connected to the public internet ;-)
>>
>>
>> Yes, good case!
>> But I think that it will not work with Chrome now:
>> https://developer.mozilla.org/en-US/docs/Web/API/Push_API/Using_the_Push_API#Extra_steps_for_Chrome_support
>> Hope that it will be possible with Firefox, but I need to double check it.
>>
>
> We could offer a little decorator, if the user explicitly wants a customer
> server :)
>
> We did that for simple push too:
>
> https://github.com/aerogear/aerogear-js/blob/master/src/simplepush/aerogear.simplepush.js#L27
>

Great!

So, I will begin to implement Chrome support for UPS, right? PR against
master? Will we create JIRAs? Which labels should I use?

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

On Tue, May 17, 2016 at 9:29 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
> On Tue, May 17, 2016 at 7:03 PM, Idel Pivnitskiy <
> idel.pivnitskiy at gmail.com> wrote:
>
>> Right, but that goes through their service. I think one of the big
>>> advantages here is that with a truly open WebPush Server/Protocol/API, you
>>> as a company, can run your own, inpendent push network. Having support to
>>> connect to a custom WebPush server from the (standard?) JS API would be
>>> nice. Makes you more independent.
>>> E.g. imagine push on a private network, where not all devcies are
>>> connected to the public internet ;-)
>>
>>
>> Yes, good case!
>> But I think that it will not work with Chrome now:
>> https://developer.mozilla.org/en-US/docs/Web/API/Push_API/Using_the_Push_API#Extra_steps_for_Chrome_support
>> Hope that it will be possible with Firefox, but I need to double check it.
>>
>
> We could offer a little decorator, if the user explicitly wants a customer
> server :)
>
> We did that for simple push too:
>
> https://github.com/aerogear/aerogear-js/blob/master/src/simplepush/aerogear.simplepush.js#L27
>
>
>
>>
>> Best regards,
>> Idel Pivnitskiy
>> --
>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>>
>> On Tue, May 17, 2016 at 7:45 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>>
>>>
>>> On Tue, May 17, 2016 at 6:03 PM, Idel Pivnitskiy <
>>> idel.pivnitskiy at gmail.com> wrote:
>>>
>>>> Does it make sense starting with more focused examples? Showing
>>>>> Chrome/Firefox receiving message via the WebPush APIs from the standalone
>>>>> WebPush Server ?
>>>>
>>>>
>>>> I think that we don't need our WebPush Server for Chrome/Firefox
>>>> support. Because it possible to send push messages to Chrome only
>>>> through GCM, using their API-key.
>>>>
>>>
>>> Right, but that goes through their service. I think one of the big
>>> advantages here is that with a truly open WebPush Server/Protocol/API, you
>>> as a company, can run your own, inpendent push network. Having support to
>>> connect to a custom WebPush server from the (standard?) JS API would be
>>> nice. Makes you more independent.
>>>
>>> E.g. imagine push on a private network, where not all devcies are
>>> connected to the public internet ;-)
>>>
>>> Not a high priority, but IMO worth to think about this
>>>
>>>
>>>>
>>>>
>>>>> I think we can also remove the SimplePush from the master branch of
>>>>> UPS, while on this project, no ?
>>>>
>>>>
>>>> Think that it could be done at the end of the summer, if there are no
>>>> reasons to keep it. After or during the integration of WebPush Server to
>>>> UPS. I prefer after, like it was with Doclet and Miredot.
>>>>
>>>
>>> +1 makes sense to remove SimplePush, once WebPush is around. WebPush is
>>> the successor of SimplePush in general
>>>
>>>>
>>>>
>>>>
>>>> Best regards,
>>>> Idel Pivnitskiy
>>>> --
>>>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>>>> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>>>>
>>>> On Tue, May 17, 2016 at 6:38 PM, Matthias Wessendorf <matzew at apache.org
>>>> > wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>>
>>>>> On Tue, May 17, 2016 at 5:33 PM, Idel Pivnitskiy <
>>>>> idel.pivnitskiy at gmail.com> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I've come back from the little vocation and ready for the work on my
>>>>>> GSoC project.
>>>>>>
>>>>>> What will be our plan?
>>>>>> I may work according to my proposal: the first steps will be the
>>>>>> adding WebPush support for Chrome and Firefox directly to UPS (through
>>>>>> Google Cloud Messaging and Mozilla Push Service).
>>>>>>
>>>>>
>>>>> I like that, but
>>>>>
>>>>>
>>>>>> Another way: I may begin my work from WebPush Server.
>>>>>>
>>>>>
>>>>> Does it make sense starting with more focused examples? Showing
>>>>> Chrome/Firefox receiving message via the WebPush APIs from the standalone
>>>>> WebPush Server ?
>>>>>
>>>>>
>>>>> At the end of the day, UPS is just another 'driver', triggering the
>>>>> push ?
>>>>>
>>>>>
>>>>> Oh, I think we can also remove the SimplePush from the master branch
>>>>> of UPS, while on this project, no ?
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> If we will begin from UPS, from which branch should I work? And for
>>>>>> which release?
>>>>>>
>>>>>> 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
>>>>>
>>>>> _______________________________________________
>>>>> 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
>
> _______________________________________________
> 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/20160518/348ab792/attachment.html 

From matzew at apache.org  Wed May 18 07:31:25 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 18 May 2016 13:31:25 +0200
Subject: [aerogear-dev] GSoC plan for WebPush
In-Reply-To: <CAN+BUJpDK3cgPFJuS2E7UavyLuN_F1LQ9ShFwTZ-fKeNRU9EvQ@mail.gmail.com>
References: <CAN+BUJpj+Nd_E67un6dm2xzZO6dNf5YvH7xiQmuMZX4iaMonSQ@mail.gmail.com>
	<CAAg5f2Rg=zjVzxJtGOUBMx6rsbyLQ9q3yeee+J1tNp6ZPFQrVw@mail.gmail.com>
	<CAN+BUJpaHq1cpQq6v5-aZPmTKqO6Zv-ULOi+uYY+bw+d9MKWig@mail.gmail.com>
	<CAAg5f2TMpu4fZN16-a3UmFRq53S0JPsoiW46TSzRxarqbsNRYw@mail.gmail.com>
	<CAN+BUJqWBwWV947bW+QrJizDiMo_WjbuMH6KoNOSud-gqUtV0w@mail.gmail.com>
	<CAAg5f2QSi_Q1mk5cHRjL4W9gmk4vUF-N_6GOVEQncyUA8_aE8g@mail.gmail.com>
	<CAN+BUJpDK3cgPFJuS2E7UavyLuN_F1LQ9ShFwTZ-fKeNRU9EvQ@mail.gmail.com>
Message-ID: <CAAg5f2S+MkVathfzJmEOWVFmyBSZmFHz=fsFgEWJDMsw+=pLBQ@mail.gmail.com>

On Wed, May 18, 2016 at 12:48 PM, Idel Pivnitskiy <idel.pivnitskiy at gmail.com
> wrote:

> Right, but that goes through their service. I think one of the big
>>>> advantages here is that with a truly open WebPush Server/Protocol/API, you
>>>> as a company, can run your own, inpendent push network. Having support to
>>>> connect to a custom WebPush server from the (standard?) JS API would be
>>>> nice. Makes you more independent.
>>>> E.g. imagine push on a private network, where not all devcies are
>>>> connected to the public internet ;-)
>>>
>>>
>>> Yes, good case!
>>> But I think that it will not work with Chrome now:
>>> https://developer.mozilla.org/en-US/docs/Web/API/Push_API/Using_the_Push_API#Extra_steps_for_Chrome_support
>>> Hope that it will be possible with Firefox, but I need to double check
>>> it.
>>>
>>
>> We could offer a little decorator, if the user explicitly wants a
>> customer server :)
>>
>> We did that for simple push too:
>>
>> https://github.com/aerogear/aerogear-js/blob/master/src/simplepush/aerogear.simplepush.js#L27
>>
>
> Great!
>
> So, I will begin to implement Chrome support for UPS, right? PR against
> master?
>

sounds good to me!

For HTTP/2 I think we may need to add instructions about adding the
jetty-alpn-agent, for getting WF-10 up and running


> Will we create JIRAs? Which labels should I use?
>
> Best regards,
> Idel Pivnitskiy
> --
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>
> On Tue, May 17, 2016 at 9:29 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>> On Tue, May 17, 2016 at 7:03 PM, Idel Pivnitskiy <
>> idel.pivnitskiy at gmail.com> wrote:
>>
>>> Right, but that goes through their service. I think one of the big
>>>> advantages here is that with a truly open WebPush Server/Protocol/API, you
>>>> as a company, can run your own, inpendent push network. Having support to
>>>> connect to a custom WebPush server from the (standard?) JS API would be
>>>> nice. Makes you more independent.
>>>> E.g. imagine push on a private network, where not all devcies are
>>>> connected to the public internet ;-)
>>>
>>>
>>> Yes, good case!
>>> But I think that it will not work with Chrome now:
>>> https://developer.mozilla.org/en-US/docs/Web/API/Push_API/Using_the_Push_API#Extra_steps_for_Chrome_support
>>> Hope that it will be possible with Firefox, but I need to double check
>>> it.
>>>
>>
>> We could offer a little decorator, if the user explicitly wants a
>> customer server :)
>>
>> We did that for simple push too:
>>
>> https://github.com/aerogear/aerogear-js/blob/master/src/simplepush/aerogear.simplepush.js#L27
>>
>>
>>
>>>
>>> Best regards,
>>> Idel Pivnitskiy
>>> --
>>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>>> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>>>
>>> On Tue, May 17, 2016 at 7:45 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Tue, May 17, 2016 at 6:03 PM, Idel Pivnitskiy <
>>>> idel.pivnitskiy at gmail.com> wrote:
>>>>
>>>>> Does it make sense starting with more focused examples? Showing
>>>>>> Chrome/Firefox receiving message via the WebPush APIs from the standalone
>>>>>> WebPush Server ?
>>>>>
>>>>>
>>>>> I think that we don't need our WebPush Server for Chrome/Firefox
>>>>> support. Because it possible to send push messages to Chrome only
>>>>> through GCM, using their API-key.
>>>>>
>>>>
>>>> Right, but that goes through their service. I think one of the big
>>>> advantages here is that with a truly open WebPush Server/Protocol/API, you
>>>> as a company, can run your own, inpendent push network. Having support to
>>>> connect to a custom WebPush server from the (standard?) JS API would be
>>>> nice. Makes you more independent.
>>>>
>>>> E.g. imagine push on a private network, where not all devcies are
>>>> connected to the public internet ;-)
>>>>
>>>> Not a high priority, but IMO worth to think about this
>>>>
>>>>
>>>>>
>>>>>
>>>>>> I think we can also remove the SimplePush from the master branch of
>>>>>> UPS, while on this project, no ?
>>>>>
>>>>>
>>>>> Think that it could be done at the end of the summer, if there are no
>>>>> reasons to keep it. After or during the integration of WebPush Server to
>>>>> UPS. I prefer after, like it was with Doclet and Miredot.
>>>>>
>>>>
>>>> +1 makes sense to remove SimplePush, once WebPush is around. WebPush is
>>>> the successor of SimplePush in general
>>>>
>>>>>
>>>>>
>>>>>
>>>>> Best regards,
>>>>> Idel Pivnitskiy
>>>>> --
>>>>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>>>>> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>>>>>
>>>>> On Tue, May 17, 2016 at 6:38 PM, Matthias Wessendorf <
>>>>> matzew at apache.org> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, May 17, 2016 at 5:33 PM, Idel Pivnitskiy <
>>>>>> idel.pivnitskiy at gmail.com> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I've come back from the little vocation and ready for the work on my
>>>>>>> GSoC project.
>>>>>>>
>>>>>>> What will be our plan?
>>>>>>> I may work according to my proposal: the first steps will be the
>>>>>>> adding WebPush support for Chrome and Firefox directly to UPS (through
>>>>>>> Google Cloud Messaging and Mozilla Push Service).
>>>>>>>
>>>>>>
>>>>>> I like that, but
>>>>>>
>>>>>>
>>>>>>> Another way: I may begin my work from WebPush Server.
>>>>>>>
>>>>>>
>>>>>> Does it make sense starting with more focused examples? Showing
>>>>>> Chrome/Firefox receiving message via the WebPush APIs from the standalone
>>>>>> WebPush Server ?
>>>>>>
>>>>>>
>>>>>> At the end of the day, UPS is just another 'driver', triggering the
>>>>>> push ?
>>>>>>
>>>>>>
>>>>>> Oh, I think we can also remove the SimplePush from the master branch
>>>>>> of UPS, while on this project, no ?
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> If we will begin from UPS, from which branch should I work? And for
>>>>>>> which release?
>>>>>>>
>>>>>>> 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
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>
>> _______________________________________________
>> 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/20160518/d4c6a8f1/attachment-0001.html 

From matzew at apache.org  Wed May 18 07:31:59 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 18 May 2016 13:31:59 +0200
Subject: [aerogear-dev] GSoC plan for WebPush
In-Reply-To: <CAAg5f2S+MkVathfzJmEOWVFmyBSZmFHz=fsFgEWJDMsw+=pLBQ@mail.gmail.com>
References: <CAN+BUJpj+Nd_E67un6dm2xzZO6dNf5YvH7xiQmuMZX4iaMonSQ@mail.gmail.com>
	<CAAg5f2Rg=zjVzxJtGOUBMx6rsbyLQ9q3yeee+J1tNp6ZPFQrVw@mail.gmail.com>
	<CAN+BUJpaHq1cpQq6v5-aZPmTKqO6Zv-ULOi+uYY+bw+d9MKWig@mail.gmail.com>
	<CAAg5f2TMpu4fZN16-a3UmFRq53S0JPsoiW46TSzRxarqbsNRYw@mail.gmail.com>
	<CAN+BUJqWBwWV947bW+QrJizDiMo_WjbuMH6KoNOSud-gqUtV0w@mail.gmail.com>
	<CAAg5f2QSi_Q1mk5cHRjL4W9gmk4vUF-N_6GOVEQncyUA8_aE8g@mail.gmail.com>
	<CAN+BUJpDK3cgPFJuS2E7UavyLuN_F1LQ9ShFwTZ-fKeNRU9EvQ@mail.gmail.com>
	<CAAg5f2S+MkVathfzJmEOWVFmyBSZmFHz=fsFgEWJDMsw+=pLBQ@mail.gmail.com>
Message-ID: <CAAg5f2S9rHjQhdqJSGy+i7-Sxp0Smhn-zcEkLZUiEzyeOSbbVA@mail.gmail.com>

@JIRA: sure, please on AGPUSH; we can use the label 'gsoc-webpush' ?

On Wed, May 18, 2016 at 1:31 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Wed, May 18, 2016 at 12:48 PM, Idel Pivnitskiy <
> idel.pivnitskiy at gmail.com> wrote:
>
>> Right, but that goes through their service. I think one of the big
>>>>> advantages here is that with a truly open WebPush Server/Protocol/API, you
>>>>> as a company, can run your own, inpendent push network. Having support to
>>>>> connect to a custom WebPush server from the (standard?) JS API would be
>>>>> nice. Makes you more independent.
>>>>> E.g. imagine push on a private network, where not all devcies are
>>>>> connected to the public internet ;-)
>>>>
>>>>
>>>> Yes, good case!
>>>> But I think that it will not work with Chrome now:
>>>> https://developer.mozilla.org/en-US/docs/Web/API/Push_API/Using_the_Push_API#Extra_steps_for_Chrome_support
>>>> Hope that it will be possible with Firefox, but I need to double check
>>>> it.
>>>>
>>>
>>> We could offer a little decorator, if the user explicitly wants a
>>> customer server :)
>>>
>>> We did that for simple push too:
>>>
>>> https://github.com/aerogear/aerogear-js/blob/master/src/simplepush/aerogear.simplepush.js#L27
>>>
>>
>> Great!
>>
>> So, I will begin to implement Chrome support for UPS, right? PR against
>> master?
>>
>
> sounds good to me!
>
> For HTTP/2 I think we may need to add instructions about adding the
> jetty-alpn-agent, for getting WF-10 up and running
>
>
>> Will we create JIRAs? Which labels should I use?
>>
>> Best regards,
>> Idel Pivnitskiy
>> --
>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>>
>> On Tue, May 17, 2016 at 9:29 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>>
>>> On Tue, May 17, 2016 at 7:03 PM, Idel Pivnitskiy <
>>> idel.pivnitskiy at gmail.com> wrote:
>>>
>>>> Right, but that goes through their service. I think one of the big
>>>>> advantages here is that with a truly open WebPush Server/Protocol/API, you
>>>>> as a company, can run your own, inpendent push network. Having support to
>>>>> connect to a custom WebPush server from the (standard?) JS API would be
>>>>> nice. Makes you more independent.
>>>>> E.g. imagine push on a private network, where not all devcies are
>>>>> connected to the public internet ;-)
>>>>
>>>>
>>>> Yes, good case!
>>>> But I think that it will not work with Chrome now:
>>>> https://developer.mozilla.org/en-US/docs/Web/API/Push_API/Using_the_Push_API#Extra_steps_for_Chrome_support
>>>> Hope that it will be possible with Firefox, but I need to double check
>>>> it.
>>>>
>>>
>>> We could offer a little decorator, if the user explicitly wants a
>>> customer server :)
>>>
>>> We did that for simple push too:
>>>
>>> https://github.com/aerogear/aerogear-js/blob/master/src/simplepush/aerogear.simplepush.js#L27
>>>
>>>
>>>
>>>>
>>>> Best regards,
>>>> Idel Pivnitskiy
>>>> --
>>>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>>>> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>>>>
>>>> On Tue, May 17, 2016 at 7:45 PM, Matthias Wessendorf <matzew at apache.org
>>>> > wrote:
>>>>
>>>>>
>>>>>
>>>>> On Tue, May 17, 2016 at 6:03 PM, Idel Pivnitskiy <
>>>>> idel.pivnitskiy at gmail.com> wrote:
>>>>>
>>>>>> Does it make sense starting with more focused examples? Showing
>>>>>>> Chrome/Firefox receiving message via the WebPush APIs from the standalone
>>>>>>> WebPush Server ?
>>>>>>
>>>>>>
>>>>>> I think that we don't need our WebPush Server for Chrome/Firefox
>>>>>> support. Because it possible to send push messages to Chrome only
>>>>>> through GCM, using their API-key.
>>>>>>
>>>>>
>>>>> Right, but that goes through their service. I think one of the big
>>>>> advantages here is that with a truly open WebPush Server/Protocol/API, you
>>>>> as a company, can run your own, inpendent push network. Having support to
>>>>> connect to a custom WebPush server from the (standard?) JS API would be
>>>>> nice. Makes you more independent.
>>>>>
>>>>> E.g. imagine push on a private network, where not all devcies are
>>>>> connected to the public internet ;-)
>>>>>
>>>>> Not a high priority, but IMO worth to think about this
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>>> I think we can also remove the SimplePush from the master branch of
>>>>>>> UPS, while on this project, no ?
>>>>>>
>>>>>>
>>>>>> Think that it could be done at the end of the summer, if there are no
>>>>>> reasons to keep it. After or during the integration of WebPush Server to
>>>>>> UPS. I prefer after, like it was with Doclet and Miredot.
>>>>>>
>>>>>
>>>>> +1 makes sense to remove SimplePush, once WebPush is around. WebPush
>>>>> is the successor of SimplePush in general
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Best regards,
>>>>>> Idel Pivnitskiy
>>>>>> --
>>>>>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>>>>>> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>>>>>>
>>>>>> On Tue, May 17, 2016 at 6:38 PM, Matthias Wessendorf <
>>>>>> matzew at apache.org> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, May 17, 2016 at 5:33 PM, Idel Pivnitskiy <
>>>>>>> idel.pivnitskiy at gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> I've come back from the little vocation and ready for the work on
>>>>>>>> my GSoC project.
>>>>>>>>
>>>>>>>> What will be our plan?
>>>>>>>> I may work according to my proposal: the first steps will be the
>>>>>>>> adding WebPush support for Chrome and Firefox directly to UPS (through
>>>>>>>> Google Cloud Messaging and Mozilla Push Service).
>>>>>>>>
>>>>>>>
>>>>>>> I like that, but
>>>>>>>
>>>>>>>
>>>>>>>> Another way: I may begin my work from WebPush Server.
>>>>>>>>
>>>>>>>
>>>>>>> Does it make sense starting with more focused examples? Showing
>>>>>>> Chrome/Firefox receiving message via the WebPush APIs from the standalone
>>>>>>> WebPush Server ?
>>>>>>>
>>>>>>>
>>>>>>> At the end of the day, UPS is just another 'driver', triggering the
>>>>>>> push ?
>>>>>>>
>>>>>>>
>>>>>>> Oh, I think we can also remove the SimplePush from the master branch
>>>>>>> of UPS, while on this project, no ?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> If we will begin from UPS, from which branch should I work? And for
>>>>>>>> which release?
>>>>>>>>
>>>>>>>> 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
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>
>>> _______________________________________________
>>> 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/20160518/c1120b42/attachment-0001.html 

From lholmqui at redhat.com  Wed May 18 09:28:23 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Wed, 18 May 2016 09:28:23 -0400
Subject: [aerogear-dev] UPS/Keycloak Decouple status?
Message-ID: <CALD3Fd0wythf2F8U_0vnOe3dVfEQ-TuB64c-b-5iPNcfo0yjuw@mail.gmail.com>

Hey peeps.

while i was doing some work on the node admin client i just cretated, i was
think about this $SUBJECT and saw that the PR is still open,
https://github.com/aerogear/aerogear-unifiedpush-server/pull/677


I know abstractj did some awesome work around this, but i wasn't sure what
the status was.

i see it's been open for a while.


-Luke
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160518/864a1a28/attachment.html 

From matzew at apache.org  Wed May 18 17:04:11 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 18 May 2016 23:04:11 +0200
Subject: [aerogear-dev] UPS/Keycloak Decouple status?
In-Reply-To: <CALD3Fd0wythf2F8U_0vnOe3dVfEQ-TuB64c-b-5iPNcfo0yjuw@mail.gmail.com>
References: <CALD3Fd0wythf2F8U_0vnOe3dVfEQ-TuB64c-b-5iPNcfo0yjuw@mail.gmail.com>
Message-ID: <CAAg5f2Ro=EcV3qLOJ7g5y7FywpDSpoZXM8X-aYgw_QhuEbY-OQ@mail.gmail.com>

yes, I know it's been open for quite some time :-(

I will try to see if I can update to 1.9.x and than we can merge to master.
It's a good start to get the decouple for a future 1.2.0 release on the
1.2.0.alphp-2

On Wed, May 18, 2016 at 3:28 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> Hey peeps.
>
> while i was doing some work on the node admin client i just cretated, i
> was think about this $SUBJECT and saw that the PR is still open,
> https://github.com/aerogear/aerogear-unifiedpush-server/pull/677
>
>
> I know abstractj did some awesome work around this, but i wasn't sure what
> the status was.
>
> i see it's been open for a while.
>
>
> -Luke
>
>
>
>
> _______________________________________________
> 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/20160518/70b0e83b/attachment.html 

From lholmqui at redhat.com  Thu May 19 15:21:04 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 19 May 2016 15:21:04 -0400
Subject: [aerogear-dev] Variant Updates return 200 but docs say 204
Message-ID: <CALD3Fd18QPKjnXOzSrGbRMZXSwGhB4dDB-gP_TA7_drg0Dpr9w@mail.gmail.com>

The variant update endpoint returns a 200 with the updated content, but the
docs says it should return a 204 with no Content

i've create a JIRA for it,  https://issues.jboss.org/browse/AGPUSH-1635


I think PUT's are suppose to be 204's, but there might be things relying on
the fact that the update returns data,

here is a link to the AndroidVariants update endpoint,
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/AndroidVariantEndpoint.java#L142
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160519/47640211/attachment.html 

From matzew at apache.org  Thu May 19 16:09:17 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 19 May 2016 22:09:17 +0200
Subject: [aerogear-dev] Variant Updates return 200 but docs say 204
In-Reply-To: <CALD3Fd18QPKjnXOzSrGbRMZXSwGhB4dDB-gP_TA7_drg0Dpr9w@mail.gmail.com>
References: <CALD3Fd18QPKjnXOzSrGbRMZXSwGhB4dDB-gP_TA7_drg0Dpr9w@mail.gmail.com>
Message-ID: <CAAg5f2RE8N09sPZzxqugecqD5i6SqdfT96p967_cJHu1bE=74w@mail.gmail.com>

we changed that last year:
https://github.com/aerogear/aerogear-unifiedpush-server/pull/651

Systems that integrate with the UPS might appreciate the actual response
data of the updated entity, so we moved to 200 status code.

The doc is broken. Good find Luke.

Mind sending a doc patch ?

On Thu, May 19, 2016 at 9:21 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> The variant update endpoint returns a 200 with the updated content, but
> the docs says it should return a 204 with no Content
>
> i've create a JIRA for it,  https://issues.jboss.org/browse/AGPUSH-1635
>
>
> I think PUT's are suppose to be 204's, but there might be things relying
> on the fact that the update returns data,
>
> here is a link to the AndroidVariants update endpoint,
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/AndroidVariantEndpoint.java#L142
>
> _______________________________________________
> 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/20160519/c226bfe3/attachment.html 

From lholmqui at redhat.com  Thu May 19 16:10:47 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 19 May 2016 16:10:47 -0400
Subject: [aerogear-dev] Variant Updates return 200 but docs say 204
In-Reply-To: <CAAg5f2RE8N09sPZzxqugecqD5i6SqdfT96p967_cJHu1bE=74w@mail.gmail.com>
References: <CALD3Fd18QPKjnXOzSrGbRMZXSwGhB4dDB-gP_TA7_drg0Dpr9w@mail.gmail.com>
	<CAAg5f2RE8N09sPZzxqugecqD5i6SqdfT96p967_cJHu1bE=74w@mail.gmail.com>
Message-ID: <CALD3Fd3SrohiCt4VNp0LoeX9noBHCm4jeXALEAsnu_7N3z26Uw@mail.gmail.com>

On Thu, May 19, 2016 at 4:09 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> we changed that last year:
> https://github.com/aerogear/aerogear-unifiedpush-server/pull/651
>

i thought it sounded familiar

>
>
> Systems that integrate with the UPS might appreciate the actual response
> data of the updated entity, so we moved to 200 status code.
>
> The doc is broken. Good find Luke.
>
> Mind sending a doc patch ?
>

Doc Patch incoming

>
> On Thu, May 19, 2016 at 9:21 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> The variant update endpoint returns a 200 with the updated content, but
>> the docs says it should return a 204 with no Content
>>
>> i've create a JIRA for it,  https://issues.jboss.org/browse/AGPUSH-1635
>>
>>
>> I think PUT's are suppose to be 204's, but there might be things relying
>> on the fact that the update returns data,
>>
>> here is a link to the AndroidVariants update endpoint,
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/AndroidVariantEndpoint.java#L142
>>
>> _______________________________________________
>> 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/20160519/7a0f0532/attachment.html 

From lholmqui at redhat.com  Thu May 19 16:23:22 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 19 May 2016 16:23:22 -0400
Subject: [aerogear-dev] Variant Updates return 200 but docs say 204
In-Reply-To: <CALD3Fd3SrohiCt4VNp0LoeX9noBHCm4jeXALEAsnu_7N3z26Uw@mail.gmail.com>
References: <CALD3Fd18QPKjnXOzSrGbRMZXSwGhB4dDB-gP_TA7_drg0Dpr9w@mail.gmail.com>
	<CAAg5f2RE8N09sPZzxqugecqD5i6SqdfT96p967_cJHu1bE=74w@mail.gmail.com>
	<CALD3Fd3SrohiCt4VNp0LoeX9noBHCm4jeXALEAsnu_7N3z26Uw@mail.gmail.com>
Message-ID: <CALD3Fd0MzcK_-GRYHZehoZmAUoGiqA0Q+erpSgULEKiUzXRVSQ@mail.gmail.com>

https://github.com/aerogear/aerogear-unifiedpush-server/pull/726

On Thu, May 19, 2016 at 4:10 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

>
>
> On Thu, May 19, 2016 at 4:09 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> we changed that last year:
>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/651
>>
>
> i thought it sounded familiar
>
>>
>>
>> Systems that integrate with the UPS might appreciate the actual response
>> data of the updated entity, so we moved to 200 status code.
>>
>> The doc is broken. Good find Luke.
>>
>> Mind sending a doc patch ?
>>
>
> Doc Patch incoming
>
>>
>> On Thu, May 19, 2016 at 9:21 PM, Luke Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>> The variant update endpoint returns a 200 with the updated content, but
>>> the docs says it should return a 204 with no Content
>>>
>>> i've create a JIRA for it,  https://issues.jboss.org/browse/AGPUSH-1635
>>>
>>>
>>> I think PUT's are suppose to be 204's, but there might be things relying
>>> on the fact that the update returns data,
>>>
>>> here is a link to the AndroidVariants update endpoint,
>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/AndroidVariantEndpoint.java#L142
>>>
>>> _______________________________________________
>>> 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/20160519/4fc5034a/attachment-0001.html 

From matzew at apache.org  Fri May 20 02:52:40 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 20 May 2016 08:52:40 +0200
Subject: [aerogear-dev] Android Push: Firebase Cloud Messaging
Message-ID: <CAAg5f2T5Y2VgrLDYc1y+eg5_KiX63d6+eO3V1qAHz9rCFR--Ag@mail.gmail.com>

Hi,

Wednesday at Google IO, Google did announce the availability of Firebase
Cloud Messaging (FCM), which deprecates Google Cloud Messaging (GCM).

Here is a quite from the GCM documentation website:

>>
Firebase Cloud Messaging (FCM) is the new version of GCM. It inherits the
reliable and scalable GCM infrastructure, plus new features! See the FAQ to
learn more. If you are integrating messaging in a new app, start with FCM.
GCM users are strongly recommended to upgrade to FCM, in order to benefit
from new FCM features today and in the future.
<<

At the core FCM is basically the same as GCM-3 (e.g. topic support), but
there are some changes especially in the client SDKs. I've created a few
JIRAs to scope the body of work, needed to deliver FCM support on our SDKs,
as well keeping our server and documentation in sync with the latest
offering: https://issues.jboss.org/issues/?filter=12327296

Greetings,
Matthias

* https://firebase.google.com/docs/cloud-messaging/
* https://developers.google.com/cloud-messaging/


-- 
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/20160520/83e3716c/attachment.html 

From matzew at apache.org  Wed May 25 02:45:00 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 25 May 2016 08:45:00 +0200
Subject: [aerogear-dev] SimplePush: are we done with it ?
Message-ID: <CAAg5f2SXwJY-ESMQtEdYFnsjOahFO5gj2WFkH_d74TTqKpXsBA@mail.gmail.com>

Hi,

I wonder if we should call it a day on our SimplePush efforts?

We had a 0.12.1 release in November 2014:
https://github.com/aerogear/aerogear-simplepush-server/releases

and the latest commit to the source code was in February 2015:
https://github.com/aerogear/aerogear-simplepush-server/commits/master


We do have some open JIRAs for a potential 0.13 release, as well as some
future tickets:
* https://issues.jboss.org/projects/AGPUSH/versions/12326562
* https://issues.jboss.org/projects/AGPUSH/versions/12326563


Now, that there is a follow up standard on this, WebPush, and we have a
more active community around that, and a Google Summer of Code student, I
do see this being much more interesting than SimplePush, moving forward.

I think our friends at Mozilla are also seeing much more value in focusing
on WebPush. I guess it's a bit different there as they have SimplePush in
production.


Now... what we could do it, get a last release out and instead '0.13'call
it 1.0.0, and put a note to the Github repository that this is the last
release and we stop maintaining this stuff.

Or do some really feel they want to actively continue the SimplePush server
?

I think it was a good research project and I am happy we got some momentum
around it, but I believe the future is WebPush instead of SimplePush

Feedback is more than welcome!

Matthias


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160525/40921dd3/attachment.html 

From jrconlin at gmail.com  Wed May 25 11:44:53 2016
From: jrconlin at gmail.com (JR Conlin)
Date: Wed, 25 May 2016 08:44:53 -0700
Subject: [aerogear-dev] SimplePush: are we done with it ?
In-Reply-To: <CAAg5f2SXwJY-ESMQtEdYFnsjOahFO5gj2WFkH_d74TTqKpXsBA@mail.gmail.com>
References: <CAAg5f2SXwJY-ESMQtEdYFnsjOahFO5gj2WFkH_d74TTqKpXsBA@mail.gmail.com>
Message-ID: <b900c400-9c26-2acb-0b9c-a0ecbd7c84c8@gmail.com>

Well, Mozilla is indeed focusing more on WebPush rather than Simplepush.
There are only a few products that use SimplePush at the moment, and
frankly, the feature set for WebPush makes it far more interesting.

If I may, I'd suggest focusing on areas we've seen folks struggle with,
including:

1) Data encryption -
    Not terribly surprising, but folks have problems getting ECDH
encryption and header
    publication right. I can only presume that folks that have problems
with this lead rich,
    full lives surrounded by friends and loved ones and for some
inexplicable reason, don't
    enjoy delving into frustrating bouts of brain melting math.
    Giving these poor souls a way to easily bundle up data that
endpoints can decrypt so they
    can continue their care-free lives of joy might be useful.

2) Subscriber management -
    Somewhat in hand with the previous point, dealing with subscribers
using WebPush is
    a fair bit more complicated than it would first seem. Subscribers
can have multiple endpoints
    that may shift, or simply disappear in a puff of 410 smoke. Plus,
there's the encryption keys
    that need to persist and be safe-guarded from compromise, and all
the fun that goes with
    that.

3) VAPID -
    Mozilla currently uses VAPID to allow subscription providers a way
to voluntarily provide
    info about themselves. The process involves a bit more
brain-tweaking ECDH crypto, and there
    are some considerations that might escape the casual user (Keep your
VAPID key separate from
    your publication keys; Keep your private VAPID key private;
Resubscribe your customers on key
    rotations; etc.)
    VAPID is strongly favored for how subscriptions updates would be
authorized for other service
    providers.

So, yeah, full plate. More than enough to scrape SimplePush off to make
room, and the nice bonus is that the new stuff isn't just for one
provider, and will make your library that much more attractive.

I've got a few resources to help folks get going on this:
1) https://mozilla-services.github.io/WebPushDataTestPage/ - The WebPush
Data Test Page, which is a stand alone page that encrypts a data block
and shows you as much as possible for key auditing. I recommend opening
the Browser Console, since I'm a bit verbose. That page includes VAPID
header support, but if you just wanted to see that bit:

2) http://mozilla-services.github.io/vapid/js/ - VAPID test page, which
again is stand alone and can encode and decode VAPID header claims. The
root currently has javascript and python libs, and is accepting PRs for
other languages (hint, hint). https://github.com/mozilla-services/vapid/

I'm also working on a document that (hopefully) lays out the various
steps and considerations for App Servers / subscription providers.

Does that make sense to y'all?
Thanks!

On 5/24/2016 11:45 PM, Matthias Wessendorf wrote:
> Hi,
>
> I wonder if we should call it a day on our SimplePush efforts?
>
> We had a 0.12.1 release in November 2014:
> https://github.com/aerogear/aerogear-simplepush-server/releases
>
> and the latest commit to the source code was in February 2015:
> https://github.com/aerogear/aerogear-simplepush-server/commits/master
>
>
> We do have some open JIRAs for a potential 0.13 release, as well as
> some future tickets:
> * https://issues.jboss.org/projects/AGPUSH/versions/12326562
> * https://issues.jboss.org/projects/AGPUSH/versions/12326563
>
>
> Now, that there is a follow up standard on this, WebPush, and we have
> a more active community around that, and a Google Summer of Code
> student, I do see this being much more interesting than SimplePush,
> moving forward. 
>
> I think our friends at Mozilla are also seeing much more value in
> focusing on WebPush. I guess it's a bit different there as they have
> SimplePush in production.
>
>
> Now... what we could do it, get a last release out and instead
> '0.13'call it 1.0.0, and put a note to the Github repository that this
> is the last release and we stop maintaining this stuff.
>
> Or do some really feel they want to actively continue the SimplePush
> server ?
>
> I think it was a good research project and I am happy we got some
> momentum around it, but I believe the future is WebPush instead of
> SimplePush
>
> Feedback is more than welcome!
>
> Matthias
>
>
> -- 
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf


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

From lholmqui at redhat.com  Fri May 27 15:56:16 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Fri, 27 May 2016 15:56:16 -0400
Subject: [aerogear-dev] UPS Device Registration Endpoints
Message-ID: <CALD3Fd3EomTCmo4Mte7x7ohkPkAPH+fFz3NWiXFOWbVZp3kOMA@mail.gmail.com>

thats right folks, i'm asking this question on a Friday before a Holiday
weekend(US) at 3:52(est)


i've started to implement the Device registration endpoints in node and was
just wondering what the id is here in this header


-v -H "Accept: application/json" -H "Content-type: application/json"
-H "aerogear-push-id: someid"


is it something specific, or just a random number/alpha-numeric thingy


here is the doc link for reference:
https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/#246535932


I've also decided to create this as a separate module instead of including
it in the node admin client here:
https://github.com/bucharest-gold/unifiedpush-admin-client
mostly becuase these registration endpoints don't needed to be KC
authenticated.  and they could also be used on a IOT device or something
that runs node that has webpush/simplePush or some new crazy protocol.


-Luke
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160527/1e32660b/attachment-0001.html 

From scm.blanc at gmail.com  Fri May 27 16:10:24 2016
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Fri, 27 May 2016 22:10:24 +0200
Subject: [aerogear-dev] [Aerogear-users] UPS Device Registration
	Endpoints
In-Reply-To: <CALD3Fd3EomTCmo4Mte7x7ohkPkAPH+fFz3NWiXFOWbVZp3kOMA@mail.gmail.com>
References: <CALD3Fd3EomTCmo4Mte7x7ohkPkAPH+fFz3NWiXFOWbVZp3kOMA@mail.gmail.com>
Message-ID: <F087E56F-5BCC-43BB-B3DD-5D1E95A06379@gmail.com>



Envoy? de mon iPhone

> Le 27 mai 2016 ? 21:56, Luke Holmquist <lholmqui at redhat.com> a ?crit :
> 
> thats right folks, i'm asking this question on a Friday before a Holiday weekend(US) at 3:52(est)
> 
> 
> i've started to implement the Device registration endpoints in node and was just wondering what the id is here in this header
> 
> 
> -v -H "Accept: application/json" -H "Content-type: application/json" -H "aerogear-push-id: someid"
> 
> is it something specific, or just a random number/alpha-numeric thingy
> 
> 
> here is the doc link for reference: https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/#246535932
Let's wait for Matzew to confirm but I think you can ignore it. Looks like a left over from our first analytics implementation , we use now a separate endpoint (the PUT) and pass this ID as a path parameter.
We probably need to clean up the javadoc
> 
> 
> I've also decided to create this as a separate module instead of including it in the node admin client here: https://github.com/bucharest-gold/unifiedpush-admin-client
> mostly becuase these registration endpoints don't needed to be KC authenticated.  and they could also be used on a IOT device or something that runs node that has webpush/simplePush or some new crazy protocol.
Make sense , I like that 
> 
> 
> -Luke
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160527/4bb13f8f/attachment.html 

From matzew at apache.org  Sat May 28 00:50:43 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Sat, 28 May 2016 06:50:43 +0200
Subject: [aerogear-dev] [Aerogear-users] UPS Device Registration
	Endpoints
In-Reply-To: <F087E56F-5BCC-43BB-B3DD-5D1E95A06379@gmail.com>
References: <CALD3Fd3EomTCmo4Mte7x7ohkPkAPH+fFz3NWiXFOWbVZp3kOMA@mail.gmail.com>
	<F087E56F-5BCC-43BB-B3DD-5D1E95A06379@gmail.com>
Message-ID: <CAAg5f2TteiGiE680MYGy7P7=kZfpdYAKcJLm-_JMrwQpAaFoow@mail.gmail.com>

On Fri, May 27, 2016 at 10:10 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

>
>
> Envoy? de mon iPhone
>
> Le 27 mai 2016 ? 21:56, Luke Holmquist <lholmqui at redhat.com> a ?crit :
>
> thats right folks, i'm asking this question on a Friday before a Holiday
> weekend(US) at 3:52(est)
>
>
> i've started to implement the Device registration endpoints in node and
> was just wondering what the id is here in this header
>
>
> -v -H "Accept: application/json" -H "Content-type: application/json" -H "aerogear-push-id: someid"
>
>
> is it something specific, or just a random number/alpha-numeric thingy
>
>
> here is the doc link for reference:
> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/#246535932
>
> Let's wait for Matzew to confirm but I think you can ignore it. Looks like
> a left over from our first analytics implementation , we use now a separate
> endpoint (the PUT) and pass this ID as a path parameter.
> We probably need to clean up the javadoc
>

correct, doc error.

the thing is only relevant here:
https://github.com/aerogear/aerogear-unifiedpush-server/blob/252c3a979cf05b69f061f7ffa6d3dcc8826c7b51/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/installations/InstallationRegistrationEndpoint.java#L203



>
>
>
> I've also decided to create this as a separate module instead of including
> it in the node admin client here:
> https://github.com/bucharest-gold/unifiedpush-admin-client
> mostly becuase these registration endpoints don't needed to be KC
> authenticated.
>
> even if they were KC managed, they would be different (E.g. just
bearer-only), since there is no relationship to the actual mgmt of the
server.

+1 on separating these two things

-M



>   and they could also be used on a IOT device or something that runs node
> that has webpush/simplePush or some new crazy protocol.
>
> Make sense , I like that
>
>
>
> -Luke
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20160528/5c140d6c/attachment.html 

From lholmqui at redhat.com  Tue May 31 15:07:19 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Tue, 31 May 2016 15:07:19 -0400
Subject: [aerogear-dev] [Aerogear-users] UPS Device Registration
	Endpoints
In-Reply-To: <CAAg5f2TteiGiE680MYGy7P7=kZfpdYAKcJLm-_JMrwQpAaFoow@mail.gmail.com>
References: <CALD3Fd3EomTCmo4Mte7x7ohkPkAPH+fFz3NWiXFOWbVZp3kOMA@mail.gmail.com>
	<F087E56F-5BCC-43BB-B3DD-5D1E95A06379@gmail.com>
	<CAAg5f2TteiGiE680MYGy7P7=kZfpdYAKcJLm-_JMrwQpAaFoow@mail.gmail.com>
Message-ID: <CALD3Fd3hN1BLFic0vFZOtVocEM11oRkPfJ21FRnDZ9b1gb-Egg@mail.gmail.com>

Thanks for the info guys.

Also i just released the 0.1.0 version of this
https://www.npmjs.com/package/unifiedpush-registration-client

a client for doing device registration.

Currently implemented is register and unregister.  i'm working on getting
the "importer" working for the next release.



On Sat, May 28, 2016 at 12:50 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Fri, May 27, 2016 at 10:10 PM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>>
>>
>> Envoy? de mon iPhone
>>
>> Le 27 mai 2016 ? 21:56, Luke Holmquist <lholmqui at redhat.com> a ?crit :
>>
>> thats right folks, i'm asking this question on a Friday before a Holiday
>> weekend(US) at 3:52(est)
>>
>>
>> i've started to implement the Device registration endpoints in node and
>> was just wondering what the id is here in this header
>>
>>
>> -v -H "Accept: application/json" -H "Content-type: application/json" -H "aerogear-push-id: someid"
>>
>>
>> is it something specific, or just a random number/alpha-numeric thingy
>>
>>
>> here is the doc link for reference:
>> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/#246535932
>>
>> Let's wait for Matzew to confirm but I think you can ignore it. Looks
>> like a left over from our first analytics implementation , we use now a
>> separate endpoint (the PUT) and pass this ID as a path parameter.
>> We probably need to clean up the javadoc
>>
>
> correct, doc error.
>
> the thing is only relevant here:
>
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/252c3a979cf05b69f061f7ffa6d3dcc8826c7b51/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/installations/InstallationRegistrationEndpoint.java#L203
>
>
>
>>
>>
>>
>> I've also decided to create this as a separate module instead of
>> including it in the node admin client here:
>> https://github.com/bucharest-gold/unifiedpush-admin-client
>> mostly becuase these registration endpoints don't needed to be KC
>> authenticated.
>>
>> even if they were KC managed, they would be different (E.g. just
> bearer-only), since there is no relationship to the actual mgmt of the
> server.
>
> +1 on separating these two things
>
> -M
>
>
>
>>   and they could also be used on a IOT device or something that runs node
>> that has webpush/simplePush or some new crazy protocol.
>>
>> Make sense , I like that
>>
>>
>>
>> -Luke
>>
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> 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/20160531/d925fa64/attachment-0001.html