From edewit at redhat.com  Mon Aug  3 04:03:03 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Mon, 3 Aug 2015 10:03:03 +0200
Subject: [aerogear-dev] Problem with opening Aerogear(branch -
 windows10) in Visual Studio 2015
In-Reply-To: <CAD_dpu0-hnjx7Qqto3j3RvVKbNQV+nzOOayfZNbNZ4Kh8oXNfA@mail.gmail.com>
References: <82678336.267089.1438011272919.JavaMail.zimbra@redhat.com>
	<CAD_dpu0-hnjx7Qqto3j3RvVKbNQV+nzOOayfZNbNZ4Kh8oXNfA@mail.gmail.com>
Message-ID: <CAO2B-fYu1vxJ56_hZmRZ7YJadUo+5fye8jufgTevcgp7UU+kSg@mail.gmail.com>

Hi Barbora,

Which project are you talking about?

On Tue, Jul 28, 2015 at 8:51 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Hello !
>
> I have no experience using VS 2015, our "windows" specialist, Erik, is
> currently on PTO .
> In the meantime I suggest you to open a jira ticket with a maximum of
> details here https://issues.jboss.org/browse/AGWIN that will help us to
> resolve this issue.
>
> Sebi
>
>
> On Mon, Jul 27, 2015 at 5:34 PM, Barbora Suchanova <bsuchano at redhat.com>
> wrote:
>
>> Good evening,
>> my name is Barbora Suchanova and I am working on project Keycloak. As a
>> part of my job is to develop a simple Windows Phone application
>> where I am supposed to integrate authentication through Keycloak.
>>
>> Anyway I have an issue with opening your solution of aerogear from GitHub
>> for Windows 10 in new Visual Studio 2015.(update from Visual Studio 2015 RT)
>> Week ago I was able to open in it VS 2015 RT, but now it looks like
>> impossible to migrate the project into VS 2015. Does anybody resolved this
>> issue?
>> I would like to build it and run it and don't want to install VS 2015 RT
>> again...
>>
>> Thank you in advance.
>>
>> Best regards
>> Barbora Suchanova
>> _______________________________________________
>> 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
>



-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150803/2ef64480/attachment.html 

From kpiwko at redhat.com  Mon Aug  3 10:33:56 2015
From: kpiwko at redhat.com (Karel Piwko)
Date: Mon, 3 Aug 2015 16:33:56 +0200
Subject: [aerogear-dev] UPS 1.2, GCM 3.0 Topics,
	and Google's rest-client updates
In-Reply-To: <CAEQz2CvU1FJMY9=p0Fa1rBRo-fsJ=4U5vmZJjkFcWfaHu7+Hfg@mail.gmail.com>
References: <CAEQz2CvU1FJMY9=p0Fa1rBRo-fsJ=4U5vmZJjkFcWfaHu7+Hfg@mail.gmail.com>
Message-ID: <CAPXQee6GAL=HrpH4W7En-4ki1HMf_-3c-FAHFaTH1ceO=TG9vg@mail.gmail.com>

Hello Summers,

my concern would be that this repo is Ant based and not available in Maven
Central. So a fork would indeed be needed. Other problem is that the lib
does not support supplying backend server location - but this is something
a PR can fix. In the past, I believe that we evaluated this library as an
option as well https://github.com/phonedeck/gcm4j

Cheers,

Karel


On Fri, Jul 31, 2015 at 5:04 PM, Summers Pittman <supittma at redhat.com>
wrote:

> Guys and gals,
>
> UPS is currently using a fork of Google's rest-client sample to
> communicate with Google's servers (See the previous thread UPS and
> com.ganyo:gcm-server for details**).  This is an outdated fork from
> https://github.com/google/gcm.
>
> It is in fact very outdated.  The rest client code, Message and Builder
> objects, Constant fields, and Sender code don't support all of the
> fields/errors/etc needed for GCM topics messaging.  Additionally it uses a
> deprecated field in a few places.  I've filed two* issues*** in the gcm
> project to reach out and begin work with them to resolve this in a more
> sane way.  In the meanwhile we will probably have to patch and support our
> own fork of the library.
>
> Thoughts, comments, tomatoes?
>
> PS, this will probably bump XMPP support from aerogear-android-push 3.0
> and UPS 1.2.  Please let me know if it should and i will pull those from
> the JIRA epics and we can reschedule them.
>
> Summers
>
> * https://github.com/google/gcm/issues/84
> *** https://github.com/google/gcm/issues/85
> **
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UPS-and-com-ganyo-gcm-server-td12015.html
>
> _______________________________________________
> 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/20150803/685aa5ce/attachment.html 

From supittma at redhat.com  Mon Aug  3 12:46:16 2015
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 3 Aug 2015 12:46:16 -0400
Subject: [aerogear-dev] UPS 1.2, GCM 3.0 Topics,
	and Google's rest-client updates
In-Reply-To: <CAPXQee6GAL=HrpH4W7En-4ki1HMf_-3c-FAHFaTH1ceO=TG9vg@mail.gmail.com>
References: <CAEQz2CvU1FJMY9=p0Fa1rBRo-fsJ=4U5vmZJjkFcWfaHu7+Hfg@mail.gmail.com>
	<CAPXQee6GAL=HrpH4W7En-4ki1HMf_-3c-FAHFaTH1ceO=TG9vg@mail.gmail.com>
Message-ID: <CAEQz2Ct1RCuw_cv2uQ-m_Q8ZiwZz_pG9F+yb+pk27MTo2mgUKg@mail.gmail.com>

Right now I've taken the library, replaced and with maven, removed the
samples, and slapped some topic support into it.  I'll commit to my repo
for review at some point today.

On Mon, Aug 3, 2015 at 10:33 AM, Karel Piwko <kpiwko at redhat.com> wrote:

> Hello Summers,
>
> my concern would be that this repo is Ant based and not available in Maven
> Central. So a fork would indeed be needed. Other problem is that the lib
> does not support supplying backend server location - but this is something
> a PR can fix. In the past, I believe that we evaluated this library as an
> option as well https://github.com/phonedeck/gcm4j
>
> Cheers,
>
> Karel
>
>
> On Fri, Jul 31, 2015 at 5:04 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> Guys and gals,
>>
>> UPS is currently using a fork of Google's rest-client sample to
>> communicate with Google's servers (See the previous thread UPS and
>> com.ganyo:gcm-server for details**).  This is an outdated fork from
>> https://github.com/google/gcm.
>>
>> It is in fact very outdated.  The rest client code, Message and Builder
>> objects, Constant fields, and Sender code don't support all of the
>> fields/errors/etc needed for GCM topics messaging.  Additionally it uses a
>> deprecated field in a few places.  I've filed two* issues*** in the gcm
>> project to reach out and begin work with them to resolve this in a more
>> sane way.  In the meanwhile we will probably have to patch and support our
>> own fork of the library.
>>
>> Thoughts, comments, tomatoes?
>>
>> PS, this will probably bump XMPP support from aerogear-android-push 3.0
>> and UPS 1.2.  Please let me know if it should and i will pull those from
>> the JIRA epics and we can reschedule them.
>>
>> Summers
>>
>> * https://github.com/google/gcm/issues/84
>> *** https://github.com/google/gcm/issues/85
>> **
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UPS-and-com-ganyo-gcm-server-td12015.html
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150803/bf9ef56e/attachment-0001.html 

From supittma at redhat.com  Mon Aug  3 12:46:56 2015
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 3 Aug 2015 12:46:56 -0400
Subject: [aerogear-dev] UPS 1.2, GCM 3.0 Topics,
	and Google's rest-client updates
In-Reply-To: <CAPXQee6GAL=HrpH4W7En-4ki1HMf_-3c-FAHFaTH1ceO=TG9vg@mail.gmail.com>
References: <CAEQz2CvU1FJMY9=p0Fa1rBRo-fsJ=4U5vmZJjkFcWfaHu7+Hfg@mail.gmail.com>
	<CAPXQee6GAL=HrpH4W7En-4ki1HMf_-3c-FAHFaTH1ceO=TG9vg@mail.gmail.com>
Message-ID: <CAEQz2CuF3kVnoF9HsJ7MCN8pvSE5bm=eDsQgaix4fxS+OnRgLg@mail.gmail.com>

On Mon, Aug 3, 2015 at 10:33 AM, Karel Piwko <kpiwko at redhat.com> wrote:

> Hello Summers,
>
> my concern would be that this repo is Ant based and not available in Maven
> Central. So a fork would indeed be needed. Other problem is that the lib
> does not support supplying backend server location -
>
What do you mean?

> but this is something a PR can fix. In the past, I believe that we
> evaluated this library as an option as well
> https://github.com/phonedeck/gcm4j
>
> Cheers,
>
> Karel
>
>
> On Fri, Jul 31, 2015 at 5:04 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> Guys and gals,
>>
>> UPS is currently using a fork of Google's rest-client sample to
>> communicate with Google's servers (See the previous thread UPS and
>> com.ganyo:gcm-server for details**).  This is an outdated fork from
>> https://github.com/google/gcm.
>>
>> It is in fact very outdated.  The rest client code, Message and Builder
>> objects, Constant fields, and Sender code don't support all of the
>> fields/errors/etc needed for GCM topics messaging.  Additionally it uses a
>> deprecated field in a few places.  I've filed two* issues*** in the gcm
>> project to reach out and begin work with them to resolve this in a more
>> sane way.  In the meanwhile we will probably have to patch and support our
>> own fork of the library.
>>
>> Thoughts, comments, tomatoes?
>>
>> PS, this will probably bump XMPP support from aerogear-android-push 3.0
>> and UPS 1.2.  Please let me know if it should and i will pull those from
>> the JIRA epics and we can reschedule them.
>>
>> Summers
>>
>> * https://github.com/google/gcm/issues/84
>> *** https://github.com/google/gcm/issues/85
>> **
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UPS-and-com-ganyo-gcm-server-td12015.html
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150803/a3c46f18/attachment.html 

From edewit at redhat.com  Tue Aug  4 01:42:51 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 4 Aug 2015 07:42:51 +0200
Subject: [aerogear-dev] Android UPS Variant Category Issue
In-Reply-To: <D1DEB23E.AFA6%miles_fink@unc.edu>
References: <D1DEB23E.AFA6%miles_fink@unc.edu>
Message-ID: <CAO2B-fYs2ffOaH4pWV5-ZY52tYXv7TmA6ogTFU_orn92wdwmOQ@mail.gmail.com>

Hi,

Sorry no idea, can you see the call coming into UPS to verify that all
categories are there?

On Wed, Jul 29, 2015 at 10:39 PM, Fink, Miles <mfink at email.unc.edu> wrote:

> Hi,
>
> I?ve successfully got an iOS variant to register categories for
> installations in my cordova app using the cordova PushPlugin.
>
> I?m now trying to get Android to register categories and it seemingly does
> not take. It registers the installation and alias just fine but not the
> array of categories . Anyone encountered this? Push notifications work and
> are received on the android device just no categories are shown on the
> admin UI for the installation nor do category specific notifications get
> received.
>
> I?m running:
>
>    - Unified Push Server on OpenShift v1.0.3
>    - Cordova PushPlugin v2.0.1
>
> Any suggestions / pointers would be greatly appreciated! Thanks!
>
> -Miles
>
> _______________________________________________
> 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/20150804/1ef53e58/attachment.html 

From kpiwko at redhat.com  Tue Aug  4 15:36:57 2015
From: kpiwko at redhat.com (Karel Piwko)
Date: Tue, 4 Aug 2015 21:36:57 +0200
Subject: [aerogear-dev] UPS 1.2, GCM 3.0 Topics,
	and Google's rest-client updates
In-Reply-To: <CAEQz2CuF3kVnoF9HsJ7MCN8pvSE5bm=eDsQgaix4fxS+OnRgLg@mail.gmail.com>
References: <CAEQz2CvU1FJMY9=p0Fa1rBRo-fsJ=4U5vmZJjkFcWfaHu7+Hfg@mail.gmail.com>
	<CAPXQee6GAL=HrpH4W7En-4ki1HMf_-3c-FAHFaTH1ceO=TG9vg@mail.gmail.com>
	<CAEQz2CuF3kVnoF9HsJ7MCN8pvSE5bm=eDsQgaix4fxS+OnRgLg@mail.gmail.com>
Message-ID: <CAPXQee4xSeZdwKDG0oiKrTDGV=2eDeczzdaA5WCefWBn8fjYAw@mail.gmail.com>

I mean
https://github.com/google/gcm/blob/master/client-libraries/java/rest-client/src/com/google/android/gcm/server/Constants.java#L27
which makes impossible to replace GCM backend with mocked backend for
testing purposes. Other messaging provider libraries allow that.

Karel

On Mon, Aug 3, 2015 at 6:46 PM, Summers Pittman <supittma at redhat.com> wrote:

>
>
> On Mon, Aug 3, 2015 at 10:33 AM, Karel Piwko <kpiwko at redhat.com> wrote:
>
>> Hello Summers,
>>
>> my concern would be that this repo is Ant based and not available in
>> Maven Central. So a fork would indeed be needed. Other problem is that the
>> lib does not support supplying backend server location -
>>
> What do you mean?
>
>> but this is something a PR can fix. In the past, I believe that we
>> evaluated this library as an option as well
>> https://github.com/phonedeck/gcm4j
>>
>> Cheers,
>>
>> Karel
>>
>>
>> On Fri, Jul 31, 2015 at 5:04 PM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>> Guys and gals,
>>>
>>> UPS is currently using a fork of Google's rest-client sample to
>>> communicate with Google's servers (See the previous thread UPS and
>>> com.ganyo:gcm-server for details**).  This is an outdated fork from
>>> https://github.com/google/gcm.
>>>
>>> It is in fact very outdated.  The rest client code, Message and Builder
>>> objects, Constant fields, and Sender code don't support all of the
>>> fields/errors/etc needed for GCM topics messaging.  Additionally it uses a
>>> deprecated field in a few places.  I've filed two* issues*** in the gcm
>>> project to reach out and begin work with them to resolve this in a more
>>> sane way.  In the meanwhile we will probably have to patch and support our
>>> own fork of the library.
>>>
>>> Thoughts, comments, tomatoes?
>>>
>>> PS, this will probably bump XMPP support from aerogear-android-push 3.0
>>> and UPS 1.2.  Please let me know if it should and i will pull those from
>>> the JIRA epics and we can reschedule them.
>>>
>>> Summers
>>>
>>> * https://github.com/google/gcm/issues/84
>>> *** https://github.com/google/gcm/issues/85
>>> **
>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UPS-and-com-ganyo-gcm-server-td12015.html
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150804/de8fa4a0/attachment.html 

From bsuchano at redhat.com  Thu Aug  6 02:22:50 2015
From: bsuchano at redhat.com (Barbora Suchanova)
Date: Thu, 6 Aug 2015 02:22:50 -0400 (EDT)
Subject: [aerogear-dev] Problem with opening Aerogear(branch -
 windows10) in Visual Studio 2015
In-Reply-To: <CAO2B-fYu1vxJ56_hZmRZ7YJadUo+5fye8jufgTevcgp7UU+kSg@mail.gmail.com>
References: <82678336.267089.1438011272919.JavaMail.zimbra@redhat.com>
	<CAD_dpu0-hnjx7Qqto3j3RvVKbNQV+nzOOayfZNbNZ4Kh8oXNfA@mail.gmail.com>
	<CAO2B-fYu1vxJ56_hZmRZ7YJadUo+5fye8jufgTevcgp7UU+kSg@mail.gmail.com>
Message-ID: <1749967207.2262096.1438842170669.JavaMail.zimbra@redhat.com>

Hello, 
I meant this project - https://github.com/aerogear/aerogear-windows-oauth2/tree/windows10
But it's not crucial problem, just the project is incompatible in VS 2015(it can be opened only in VS 2015 RC), 
so I built and ran your other project(Shoot'n'Share) focused on WP 8.1 just for understanding how your OAuth2.0 library
works and it's sufficient for me.
Anyway if you would know how to convert the project - to be compatible even with the VS 2015, let me know.

Thank you, 
Bara S.

----- Original Message -----
From: Erik Jan de Wit <edewit at redhat.com>
To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
Sent: Mon, 03 Aug 2015 04:03:03 -0400 (EDT)
Subject: Re: [aerogear-dev] Problem with opening Aerogear(branch - windows10) in Visual Studio 2015

Hi Barbora,

Which project are you talking about?

On Tue, Jul 28, 2015 at 8:51 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Hello !
>
> I have no experience using VS 2015, our "windows" specialist, Erik, is
> currently on PTO .
> In the meantime I suggest you to open a jira ticket with a maximum of
> details here https://issues.jboss.org/browse/AGWIN that will help us to
> resolve this issue.
>
> Sebi
>
>
> On Mon, Jul 27, 2015 at 5:34 PM, Barbora Suchanova <bsuchano at redhat.com>
> wrote:
>
>> Good evening,
>> my name is Barbora Suchanova and I am working on project Keycloak. As a
>> part of my job is to develop a simple Windows Phone application
>> where I am supposed to integrate authentication through Keycloak.
>>
>> Anyway I have an issue with opening your solution of aerogear from GitHub
>> for Windows 10 in new Visual Studio 2015.(update from Visual Studio 2015 RT)
>> Week ago I was able to open in it VS 2015 RT, but now it looks like
>> impossible to migrate the project into VS 2015. Does anybody resolved this
>> issue?
>> I would like to build it and run it and don't want to install VS 2015 RT
>> again...
>>
>> Thank you in advance.
>>
>> Best regards
>> Barbora Suchanova
>> _______________________________________________
>> 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
>



-- 
Cheers,
       Erik Jan


From edewit at redhat.com  Thu Aug  6 09:06:18 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Thu, 6 Aug 2015 15:06:18 +0200
Subject: [aerogear-dev] Problem with opening Aerogear(branch -
 windows10) in Visual Studio 2015
In-Reply-To: <1749967207.2262096.1438842170669.JavaMail.zimbra@redhat.com>
References: <82678336.267089.1438011272919.JavaMail.zimbra@redhat.com>
	<CAD_dpu0-hnjx7Qqto3j3RvVKbNQV+nzOOayfZNbNZ4Kh8oXNfA@mail.gmail.com>
	<CAO2B-fYu1vxJ56_hZmRZ7YJadUo+5fye8jufgTevcgp7UU+kSg@mail.gmail.com>
	<1749967207.2262096.1438842170669.JavaMail.zimbra@redhat.com>
Message-ID: <CAO2B-fZb2=NYs6dmp_bnFbHJrtp7DbdDv4uFq8H-zBJmbUmv8w@mail.gmail.com>

I fixed the project, had to recreate it with VS 2015 and then move all
files back into it. It seems some test are still failing, but I'm looking
into that right now

On Thu, Aug 6, 2015 at 8:22 AM, Barbora Suchanova <bsuchano at redhat.com>
wrote:

> Hello,
> I meant this project -
> https://github.com/aerogear/aerogear-windows-oauth2/tree/windows10
> But it's not crucial problem, just the project is incompatible in VS
> 2015(it can be opened only in VS 2015 RC),
> so I built and ran your other project(Shoot'n'Share) focused on WP 8.1
> just for understanding how your OAuth2.0 library
> works and it's sufficient for me.
> Anyway if you would know how to convert the project - to be compatible
> even with the VS 2015, let me know.
>
> Thank you,
> Bara S.
>
> ----- Original Message -----
> From: Erik Jan de Wit <edewit at redhat.com>
> To: AeroGear Developer Mailing List <aerogear-dev at lists.jboss.org>
> Sent: Mon, 03 Aug 2015 04:03:03 -0400 (EDT)
> Subject: Re: [aerogear-dev] Problem with opening Aerogear(branch -
> windows10) in Visual Studio 2015
>
> Hi Barbora,
>
> Which project are you talking about?
>
> On Tue, Jul 28, 2015 at 8:51 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
> > Hello !
> >
> > I have no experience using VS 2015, our "windows" specialist, Erik, is
> > currently on PTO .
> > In the meantime I suggest you to open a jira ticket with a maximum of
> > details here https://issues.jboss.org/browse/AGWIN that will help us to
> > resolve this issue.
> >
> > Sebi
> >
> >
> > On Mon, Jul 27, 2015 at 5:34 PM, Barbora Suchanova <bsuchano at redhat.com>
> > wrote:
> >
> >> Good evening,
> >> my name is Barbora Suchanova and I am working on project Keycloak. As a
> >> part of my job is to develop a simple Windows Phone application
> >> where I am supposed to integrate authentication through Keycloak.
> >>
> >> Anyway I have an issue with opening your solution of aerogear from
> GitHub
> >> for Windows 10 in new Visual Studio 2015.(update from Visual Studio
> 2015 RT)
> >> Week ago I was able to open in it VS 2015 RT, but now it looks like
> >> impossible to migrate the project into VS 2015. Does anybody resolved
> this
> >> issue?
> >> I would like to build it and run it and don't want to install VS 2015 RT
> >> again...
> >>
> >> Thank you in advance.
> >>
> >> Best regards
> >> Barbora Suchanova
> >> _______________________________________________
> >> 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
> >
>
>
>
> --
> Cheers,
>        Erik Jan
>
>


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

From supittma at redhat.com  Thu Aug  6 09:42:20 2015
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 6 Aug 2015 09:42:20 -0400
Subject: [aerogear-dev] GCM Topic Messaging in UPS
Message-ID: <CAEQz2CtzUwaRDeHYXEd++cRYAJ+MxdRDzZqbfRPZTSBtK+u77g@mail.gmail.com>

Here's a video demo :
https://www.youtube.com/watch?v=s7tXcbua_sM&feature=youtu.be

Here's the PRs :
 * UPS : https://github.com/aerogear/aerogear-unifiedpush-server/pull/626
 * AGDROID : https://github.com/aerogear/aerogear-android-push/pull/50

I would link the JIRAs but I closed those tabs ;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150806/fd420a6b/attachment.html 

From supittma at redhat.com  Thu Aug  6 09:58:32 2015
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 6 Aug 2015 09:58:32 -0400
Subject: [aerogear-dev] UPS Categories going forward
Message-ID: <CAEQz2CtXQaXpQRbbc0KsZ6ZLXPF-fkXROphA-5Sb5tR7ue6FVg@mail.gmail.com>

Y'all,

Since I now have a GCM Topic PR up I figure it is time to revisit beefing
up categories a bit.

Before we discussed enhancing the server and client APIs so one could
subscribe and unsubscribe to topics without unregistering and
reregistering.  This will require a new endpoint on UPS and new code in all
the libraries

We also discussed adding the ability to "route" messages to specific
handlers based on what category the message was sent to.  This will require
adding a field to all push messages that don't use GCM topics.  It will
also require updates on the client code.

As an aside there is also GCM support on iOS, but it is much more
complicated to set up.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150806/e96ae40a/attachment.html 

From scm.blanc at gmail.com  Thu Aug  6 10:14:02 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 6 Aug 2015 16:14:02 +0200
Subject: [aerogear-dev] UPS Categories going forward
In-Reply-To: <CAEQz2CtXQaXpQRbbc0KsZ6ZLXPF-fkXROphA-5Sb5tR7ue6FVg@mail.gmail.com>
References: <CAEQz2CtXQaXpQRbbc0KsZ6ZLXPF-fkXROphA-5Sb5tR7ue6FVg@mail.gmail.com>
Message-ID: <CAD_dpu3dyOE1_VAz9MZMWaEOavRo7CCxJgHCDjP20CYdRNE-3A@mail.gmail.com>

On Thu, Aug 6, 2015 at 3:58 PM, Summers Pittman <supittma at redhat.com> wrote:

> Y'all,
>
> Since I now have a GCM Topic PR up I figure it is time to revisit beefing
> up categories a bit.
>
> Before we discussed enhancing the server and client APIs so one could
> subscribe and unsubscribe to topics without unregistering and
> reregistering.  This will require a new endpoint on UPS and new code in all
> the libraries
>

I agree we need a  PUT /device/metadata (or smt like that) even if today we
support updating of existing installations; if you register an existing
device, it will just update its metadata
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/impl/ClientInstallationServiceImpl.java#L69-L80



>
> We also discussed adding the ability to "route" messages to specific
> handlers based on what category the message was sent to.  This will require
> adding a field to all push messages that don't use GCM topics.  It will
> also require updates on the client code.
>
Can you elaborate a bit on that or point me to previous  discussions ?

>
> As an aside there is also GCM support on iOS, but it is much more
> complicated to set up.
>
> _______________________________________________
> 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/20150806/83c70c2d/attachment.html 

From supittma at redhat.com  Thu Aug  6 10:23:38 2015
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 6 Aug 2015 10:23:38 -0400
Subject: [aerogear-dev] UPS Categories going forward
In-Reply-To: <CAD_dpu3dyOE1_VAz9MZMWaEOavRo7CCxJgHCDjP20CYdRNE-3A@mail.gmail.com>
References: <CAEQz2CtXQaXpQRbbc0KsZ6ZLXPF-fkXROphA-5Sb5tR7ue6FVg@mail.gmail.com>
	<CAD_dpu3dyOE1_VAz9MZMWaEOavRo7CCxJgHCDjP20CYdRNE-3A@mail.gmail.com>
Message-ID: <CAEQz2CtqaHdzKwtEN4K3sNn1JOyJ9JNUD4W5aDAFAZO1WhwCwA@mail.gmail.com>

On Thu, Aug 6, 2015 at 10:14 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

>
>
> On Thu, Aug 6, 2015 at 3:58 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> Y'all,
>>
>> Since I now have a GCM Topic PR up I figure it is time to revisit beefing
>> up categories a bit.
>>
>> Before we discussed enhancing the server and client APIs so one could
>> subscribe and unsubscribe to topics without unregistering and
>> reregistering.  This will require a new endpoint on UPS and new code in all
>> the libraries
>>
>
> I agree we need a  PUT /device/metadata (or smt like that) even if today
> we support updating of existing installations; if you register an existing
> device, it will just update its metadata
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/impl/ClientInstallationServiceImpl.java#L69-L80
>
>
>

Oooo.  So just spamming register is an option. Thanks!


>
>> We also discussed adding the ability to "route" messages to specific
>> handlers based on what category the message was sent to.  This will require
>> adding a field to all push messages that don't use GCM topics.  It will
>> also require updates on the client code.
>>
> Can you elaborate a bit on that or point me to previous  discussions ?
>
I was thinking of edewit's comment:

http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-topic-messaging-enhancements-AGDROID-470-td11997.html


>
>> As an aside there is also GCM support on iOS, but it is much more
>> complicated to set up.
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150806/9dab9ca6/attachment.html 

From edewit at redhat.com  Thu Aug  6 10:30:17 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Thu, 6 Aug 2015 16:30:17 +0200
Subject: [aerogear-dev] UPS Categories going forward
In-Reply-To: <CAEQz2CtqaHdzKwtEN4K3sNn1JOyJ9JNUD4W5aDAFAZO1WhwCwA@mail.gmail.com>
References: <CAEQz2CtXQaXpQRbbc0KsZ6ZLXPF-fkXROphA-5Sb5tR7ue6FVg@mail.gmail.com>
	<CAD_dpu3dyOE1_VAz9MZMWaEOavRo7CCxJgHCDjP20CYdRNE-3A@mail.gmail.com>
	<CAEQz2CtqaHdzKwtEN4K3sNn1JOyJ9JNUD4W5aDAFAZO1WhwCwA@mail.gmail.com>
Message-ID: <CAO2B-faH=U1DPRbvkAJYMteeQH1tQnJ7w8L-k+5_c_d13Y0vjg@mail.gmail.com>

+1 on this I think it's very useful to have a specific listener per
topic/category like I said before ;)

-1 on re-using register, even though that already works, I would like a new
endpoint to make it's intent more clear also, some clients need to store
things locally to be able to call register multiple times (iOS and
windows). But we could do it as an initial version.

On Thu, Aug 6, 2015 at 4:23 PM, Summers Pittman <supittma at redhat.com> wrote:

>
>
> On Thu, Aug 6, 2015 at 10:14 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>>
>>
>> On Thu, Aug 6, 2015 at 3:58 PM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>> Y'all,
>>>
>>> Since I now have a GCM Topic PR up I figure it is time to revisit
>>> beefing up categories a bit.
>>>
>>> Before we discussed enhancing the server and client APIs so one could
>>> subscribe and unsubscribe to topics without unregistering and
>>> reregistering.  This will require a new endpoint on UPS and new code in all
>>> the libraries
>>>
>>
>> I agree we need a  PUT /device/metadata (or smt like that) even if today
>> we support updating of existing installations; if you register an existing
>> device, it will just update its metadata
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/impl/ClientInstallationServiceImpl.java#L69-L80
>>
>>
>>
>
> Oooo.  So just spamming register is an option. Thanks!
>
>
>>
>>> We also discussed adding the ability to "route" messages to specific
>>> handlers based on what category the message was sent to.  This will require
>>> adding a field to all push messages that don't use GCM topics.  It will
>>> also require updates on the client code.
>>>
>> Can you elaborate a bit on that or point me to previous  discussions ?
>>
> I was thinking of edewit's comment:
>
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-topic-messaging-enhancements-AGDROID-470-td11997.html
>
>
>>
>>> As an aside there is also GCM support on iOS, but it is much more
>>> complicated to set up.
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



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

From scm.blanc at gmail.com  Thu Aug  6 10:38:20 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 6 Aug 2015 16:38:20 +0200
Subject: [aerogear-dev] UPS Categories going forward
In-Reply-To: <CAO2B-faH=U1DPRbvkAJYMteeQH1tQnJ7w8L-k+5_c_d13Y0vjg@mail.gmail.com>
References: <CAEQz2CtXQaXpQRbbc0KsZ6ZLXPF-fkXROphA-5Sb5tR7ue6FVg@mail.gmail.com>
	<CAD_dpu3dyOE1_VAz9MZMWaEOavRo7CCxJgHCDjP20CYdRNE-3A@mail.gmail.com>
	<CAEQz2CtqaHdzKwtEN4K3sNn1JOyJ9JNUD4W5aDAFAZO1WhwCwA@mail.gmail.com>
	<CAO2B-faH=U1DPRbvkAJYMteeQH1tQnJ7w8L-k+5_c_d13Y0vjg@mail.gmail.com>
Message-ID: <CAD_dpu2SWM8432bMY-4vAHbo-BEiRk5HGOVTLT-4RKXbiQVJjQ@mail.gmail.com>

Okay I see, I like the idea as well even the developer could already
implement this himself (he just pass the categories in the payload and in
the client he implements the routing).
Do we have a jira for this ?

On Thu, Aug 6, 2015 at 4:30 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> +1 on this I think it's very useful to have a specific listener per
> topic/category like I said before ;)
>
> -1 on re-using register, even though that already works, I would like a
> new endpoint to make it's intent more clear also, some clients need to
> store things locally to be able to call register multiple times (iOS and
> windows). But we could do it as an initial version.
>
> On Thu, Aug 6, 2015 at 4:23 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>>
>>
>> On Thu, Aug 6, 2015 at 10:14 AM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>>
>>>
>>> On Thu, Aug 6, 2015 at 3:58 PM, Summers Pittman <supittma at redhat.com>
>>> wrote:
>>>
>>>> Y'all,
>>>>
>>>> Since I now have a GCM Topic PR up I figure it is time to revisit
>>>> beefing up categories a bit.
>>>>
>>>> Before we discussed enhancing the server and client APIs so one could
>>>> subscribe and unsubscribe to topics without unregistering and
>>>> reregistering.  This will require a new endpoint on UPS and new code in all
>>>> the libraries
>>>>
>>>
>>> I agree we need a  PUT /device/metadata (or smt like that) even if today
>>> we support updating of existing installations; if you register an existing
>>> device, it will just update its metadata
>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/impl/ClientInstallationServiceImpl.java#L69-L80
>>>
>>>
>>>
>>
>> Oooo.  So just spamming register is an option. Thanks!
>>
>>
>>>
>>>> We also discussed adding the ability to "route" messages to specific
>>>> handlers based on what category the message was sent to.  This will require
>>>> adding a field to all push messages that don't use GCM topics.  It will
>>>> also require updates on the client code.
>>>>
>>> Can you elaborate a bit on that or point me to previous  discussions ?
>>>
>> I was thinking of edewit's comment:
>>
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-topic-messaging-enhancements-AGDROID-470-td11997.html
>>
>>
>>>
>>>> As an aside there is also GCM support on iOS, but it is much more
>>>> complicated to set up.
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> 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/20150806/dad2d4f8/attachment.html 

From supittma at redhat.com  Thu Aug  6 10:42:56 2015
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 6 Aug 2015 10:42:56 -0400
Subject: [aerogear-dev] UPS Categories going forward
In-Reply-To: <CAD_dpu2SWM8432bMY-4vAHbo-BEiRk5HGOVTLT-4RKXbiQVJjQ@mail.gmail.com>
References: <CAEQz2CtXQaXpQRbbc0KsZ6ZLXPF-fkXROphA-5Sb5tR7ue6FVg@mail.gmail.com>
	<CAD_dpu3dyOE1_VAz9MZMWaEOavRo7CCxJgHCDjP20CYdRNE-3A@mail.gmail.com>
	<CAEQz2CtqaHdzKwtEN4K3sNn1JOyJ9JNUD4W5aDAFAZO1WhwCwA@mail.gmail.com>
	<CAO2B-faH=U1DPRbvkAJYMteeQH1tQnJ7w8L-k+5_c_d13Y0vjg@mail.gmail.com>
	<CAD_dpu2SWM8432bMY-4vAHbo-BEiRk5HGOVTLT-4RKXbiQVJjQ@mail.gmail.com>
Message-ID: <CAEQz2CvvutnZkHwm_RT+SO0mw7oquTSO8aYDoBvEw_6Xmf9+wg@mail.gmail.com>

On Thu, Aug 6, 2015 at 10:38 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Okay I see, I like the idea as well even the developer could already
> implement this himself (he just pass the categories in the payload and in
> the client he implements the routing).
> Do we have a jira for this ?
>
Not yet, I can make some today.

>
> On Thu, Aug 6, 2015 at 4:30 PM, Erik Jan de Wit <edewit at redhat.com> wrote:
>
>> +1 on this I think it's very useful to have a specific listener per
>> topic/category like I said before ;)
>>
>> -1 on re-using register, even though that already works, I would like a
>> new endpoint to make it's intent more clear also, some clients need to
>> store things locally to be able to call register multiple times (iOS and
>> windows). But we could do it as an initial version.
>>
>> On Thu, Aug 6, 2015 at 4:23 PM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>>
>>>
>>> On Thu, Aug 6, 2015 at 10:14 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Thu, Aug 6, 2015 at 3:58 PM, Summers Pittman <supittma at redhat.com>
>>>> wrote:
>>>>
>>>>> Y'all,
>>>>>
>>>>> Since I now have a GCM Topic PR up I figure it is time to revisit
>>>>> beefing up categories a bit.
>>>>>
>>>>> Before we discussed enhancing the server and client APIs so one could
>>>>> subscribe and unsubscribe to topics without unregistering and
>>>>> reregistering.  This will require a new endpoint on UPS and new code in all
>>>>> the libraries
>>>>>
>>>>
>>>> I agree we need a  PUT /device/metadata (or smt like that) even if
>>>> today we support updating of existing installations; if you register an
>>>> existing device, it will just update its metadata
>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/impl/ClientInstallationServiceImpl.java#L69-L80
>>>>
>>>>
>>>>
>>>
>>> Oooo.  So just spamming register is an option. Thanks!
>>>
>>>
>>>>
>>>>> We also discussed adding the ability to "route" messages to specific
>>>>> handlers based on what category the message was sent to.  This will require
>>>>> adding a field to all push messages that don't use GCM topics.  It will
>>>>> also require updates on the client code.
>>>>>
>>>> Can you elaborate a bit on that or point me to previous  discussions ?
>>>>
>>> I was thinking of edewit's comment:
>>>
>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-topic-messaging-enhancements-AGDROID-470-td11997.html
>>>
>>>
>>>>
>>>>> As an aside there is also GCM support on iOS, but it is much more
>>>>> complicated to set up.
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Cheers,
>>        Erik Jan
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150806/fabde665/attachment.html 

From edewit at redhat.com  Thu Aug  6 10:43:45 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Thu, 6 Aug 2015 16:43:45 +0200
Subject: [aerogear-dev] UPS Categories going forward
In-Reply-To: <CAD_dpu2SWM8432bMY-4vAHbo-BEiRk5HGOVTLT-4RKXbiQVJjQ@mail.gmail.com>
References: <CAEQz2CtXQaXpQRbbc0KsZ6ZLXPF-fkXROphA-5Sb5tR7ue6FVg@mail.gmail.com>
	<CAD_dpu3dyOE1_VAz9MZMWaEOavRo7CCxJgHCDjP20CYdRNE-3A@mail.gmail.com>
	<CAEQz2CtqaHdzKwtEN4K3sNn1JOyJ9JNUD4W5aDAFAZO1WhwCwA@mail.gmail.com>
	<CAO2B-faH=U1DPRbvkAJYMteeQH1tQnJ7w8L-k+5_c_d13Y0vjg@mail.gmail.com>
	<CAD_dpu2SWM8432bMY-4vAHbo-BEiRk5HGOVTLT-4RKXbiQVJjQ@mail.gmail.com>
Message-ID: <CAO2B-fbRYhhJfppTvUHB+rGfOXUQ7-C1gBjQDdrg5XWcAbhuBg@mail.gmail.com>

Sure you can do it yourself, but now that GCM has topics and we add support
for it in the true nature of unifying it's good to have support for that on
the other platforms as well

On Thu, Aug 6, 2015 at 4:38 PM, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Okay I see, I like the idea as well even the developer could already
> implement this himself (he just pass the categories in the payload and in
> the client he implements the routing).
> Do we have a jira for this ?
>
> On Thu, Aug 6, 2015 at 4:30 PM, Erik Jan de Wit <edewit at redhat.com> wrote:
>
>> +1 on this I think it's very useful to have a specific listener per
>> topic/category like I said before ;)
>>
>> -1 on re-using register, even though that already works, I would like a
>> new endpoint to make it's intent more clear also, some clients need to
>> store things locally to be able to call register multiple times (iOS and
>> windows). But we could do it as an initial version.
>>
>> On Thu, Aug 6, 2015 at 4:23 PM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>>
>>>
>>> On Thu, Aug 6, 2015 at 10:14 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Thu, Aug 6, 2015 at 3:58 PM, Summers Pittman <supittma at redhat.com>
>>>> wrote:
>>>>
>>>>> Y'all,
>>>>>
>>>>> Since I now have a GCM Topic PR up I figure it is time to revisit
>>>>> beefing up categories a bit.
>>>>>
>>>>> Before we discussed enhancing the server and client APIs so one could
>>>>> subscribe and unsubscribe to topics without unregistering and
>>>>> reregistering.  This will require a new endpoint on UPS and new code in all
>>>>> the libraries
>>>>>
>>>>
>>>> I agree we need a  PUT /device/metadata (or smt like that) even if
>>>> today we support updating of existing installations; if you register an
>>>> existing device, it will just update its metadata
>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/impl/ClientInstallationServiceImpl.java#L69-L80
>>>>
>>>>
>>>>
>>>
>>> Oooo.  So just spamming register is an option. Thanks!
>>>
>>>
>>>>
>>>>> We also discussed adding the ability to "route" messages to specific
>>>>> handlers based on what category the message was sent to.  This will require
>>>>> adding a field to all push messages that don't use GCM topics.  It will
>>>>> also require updates on the client code.
>>>>>
>>>> Can you elaborate a bit on that or point me to previous  discussions ?
>>>>
>>> I was thinking of edewit's comment:
>>>
>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-topic-messaging-enhancements-AGDROID-470-td11997.html
>>>
>>>
>>>>
>>>>> As an aside there is also GCM support on iOS, but it is much more
>>>>> complicated to set up.
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Cheers,
>>        Erik Jan
>>
>> _______________________________________________
>> 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
>



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

From edewit at redhat.com  Fri Aug  7 07:46:48 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Fri, 7 Aug 2015 13:46:48 +0200
Subject: [aerogear-dev] windows 10
Message-ID: <CAO2B-fbJY1orypMfgo8dy5E9r=LUwAmFHumgAo2nEYYhmpZDRA@mail.gmail.com>

Hi,

After some tests we've released windows 10 support for
aerogear-windows-push and aerogear-windows-oauth2 both have been published
on nuget. With oauth2 that used to be only wnidows phone the upgrade to
windows 10 make it possible to use it on tablet and desktop, just like
push.

Hope you like it

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

From scm.blanc at gmail.com  Fri Aug  7 09:48:34 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Fri, 7 Aug 2015 15:48:34 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.0.Final
Message-ID: <CAD_dpu2N8GvrZwx9GJO4NYwA4r7=yE-Dt3LX5z+JdVRGs8vfdw@mail.gmail.com>

Hi team,

I'm happy to announce that UPS 1.1.0 Final has been staged.

Please test the staged release :

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

On Wednesday I'd like to press the button to release it to the wild.

Sebi

ps : the openshift update will follow
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150807/67c045dd/attachment.html 

From scm.blanc at gmail.com  Mon Aug 10 08:51:20 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 10 Aug 2015 14:51:20 +0200
Subject: [aerogear-dev] Staging of UnifiedPush Java Sender 1.1.0.Final
Message-ID: <CAD_dpu3Ct-vTBo0xPn8n=XbuynL8HeoxB9J+54vXTH3ok4F19A@mail.gmail.com>

Hi Team !

I'm happy to announce that the Java Sender 1.1.0.Final has been staged.

Please test the staged release :

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

On Thursday I'd like to press the magic button to release it to the wild

Thanks !

Sebi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150810/7dd3227a/attachment.html 

From lholmqui at redhat.com  Mon Aug 10 09:30:08 2015
From: lholmqui at redhat.com (Luke Holmquist)
Date: Mon, 10 Aug 2015 09:30:08 -0400
Subject: [aerogear-dev] Updated Node Sender released
Message-ID: <CALD3Fd0+E3JEoS6iJmsov3ug4QJ4-6AbKDuCAX6tAq2p4Dm6Eg@mail.gmail.com>

Now that the 1.1.0.Final release is about to be released of the UnifiedPush
Server, i've released the 0.8.0 version of the Node Sender.

This includes the new message format that the UPS needs.

you can get it in all the normal ways
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150810/22c42895/attachment.html 

From dpassos at redhat.com  Mon Aug 10 20:04:53 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Mon, 10 Aug 2015 21:04:53 -0300
Subject: [aerogear-dev] What's new in AeroGear?
Message-ID: <CADF=h2sD8k=nCd17UP736xPf0YkR5Kbf6pWZjbOv-Brx7oy0NA@mail.gmail.com>

Android

   - AeroGear Android Push 2.1.1 release
      -
      http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Android-Push-2-2-1-td12026.html
   - GCM Topics support in Android and UPS is PR?d!
      - https://github.com/aerogear/aerogear-android-push/pull/50
      - https://www.youtube.com/watch?v=s7tXcbua_sM
   - HttpStatus removed
      - https://github.com/aerogear/aerogear-android-authz/pull/34
      - https://github.com/aerogear/aerogear-android-pipe/pull/40
      - https://github.com/aerogear/aerogear-android-push/pull/48
   - Change default Encrypted Store type from Passphrase to KeyStore
      - https://github.com/aerogear/aerogear-android-store/pull/34

Push

   - UnifiedPush Server 1.1.0.Final has been staged
      -
      http://lists.jboss.org/pipermail/aerogear-dev/2015-August/011947.html
   - UnifiedPush Java Sender 1.1.0.Final has been staged
      -
      http://lists.jboss.org/pipermail/aerogear-dev/2015-August/011948.html
   - GCM Topics support in Android and UPS is PR?d!
      - https://github.com/aerogear/aerogear-unifiedpush-server/pull/626
      - https://www.youtube.com/watch?v=s7tXcbua_sM

?
-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150810/6c3755df/attachment.html 

From matzew at apache.org  Tue Aug 11 06:55:02 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 11 Aug 2015 12:55:02 +0200
Subject: [aerogear-dev] UPS 1.2, GCM 3.0 Topics,
	and Google's rest-client updates
In-Reply-To: <CAEQz2CvU1FJMY9=p0Fa1rBRo-fsJ=4U5vmZJjkFcWfaHu7+Hfg@mail.gmail.com>
References: <CAEQz2CvU1FJMY9=p0Fa1rBRo-fsJ=4U5vmZJjkFcWfaHu7+Hfg@mail.gmail.com>
Message-ID: <CAAg5f2ThMKagGnHxRqoM=eSWkvSMbVufmGLrafqRTv1hFQ2dvg@mail.gmail.com>

On Fri, Jul 31, 2015 at 5:04 PM, Summers Pittman <supittma at redhat.com>
wrote:

> Guys and gals,
>
> UPS is currently using a fork of Google's rest-client sample to
> communicate with Google's servers (See the previous thread UPS and
> com.ganyo:gcm-server for details**).  This is an outdated fork from
> https://github.com/google/gcm.
>
> It is in fact very outdated.  The rest client code, Message and Builder
> objects, Constant fields, and Sender code don't support all of the
> fields/errors/etc needed for GCM topics messaging.  Additionally it uses a
> deprecated field in a few places.  I've filed two* issues*** in the gcm
> project to reach out and begin work with them to resolve this in a more
> sane way.  In the meanwhile we will probably have to patch and support our
> own fork of the library.
>
> Thoughts, comments, tomatoes?
>
> PS, this will probably bump XMPP support from aerogear-android-push 3.0
> and UPS 1.2.  Please let me know if it should and i will pull those from
> the JIRA epics and we can reschedule them.
>

This would a work-around, but ultimately we wanna use (or create) a
GCM-XMPP library, to be used in UPS, right ?

Sure, if that takes a bit more time, let's get this scheduled for 1.3. I
think moving to XMPP, will also improve send performance, since we have one
connection (pool) instead of countless HTTP requests

-M


>
> Summers
>
> * https://github.com/google/gcm/issues/84
> *** https://github.com/google/gcm/issues/85
> **
> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UPS-and-com-ganyo-gcm-server-td12015.html
>
> _______________________________________________
> 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/20150811/a9a7d9b4/attachment-0001.html 

From matzew at apache.org  Tue Aug 11 07:00:29 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 11 Aug 2015 13:00:29 +0200
Subject: [aerogear-dev] Android UPS Variant Category Issue
In-Reply-To: <CAO2B-fYs2ffOaH4pWV5-ZY52tYXv7TmA6ogTFU_orn92wdwmOQ@mail.gmail.com>
References: <D1DEB23E.AFA6%miles_fink@unc.edu>
	<CAO2B-fYs2ffOaH4pWV5-ZY52tYXv7TmA6ogTFU_orn92wdwmOQ@mail.gmail.com>
Message-ID: <CAAg5f2QhDrhiQEM70gTetFdh8oMOJsMHVzwzvNQgNFLfX_CdwQ@mail.gmail.com>

Hi Miles,

sounds like: https://issues.jboss.org/browse/AGCORDOVA-112 ?

On Tue, Aug 4, 2015 at 7:42 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi,
>
> Sorry no idea, can you see the call coming into UPS to verify that all
> categories are there?
>
> On Wed, Jul 29, 2015 at 10:39 PM, Fink, Miles <mfink at email.unc.edu> wrote:
>
>> Hi,
>>
>> I?ve successfully got an iOS variant to register categories for
>> installations in my cordova app using the cordova PushPlugin.
>>
>> I?m now trying to get Android to register categories and it seemingly
>> does not take. It registers the installation and alias just fine but not
>> the array of categories . Anyone encountered this? Push notifications work
>> and are received on the android device just no categories are shown on the
>> admin UI for the installation nor do category specific notifications get
>> received.
>>
>> I?m running:
>>
>>    - Unified Push Server on OpenShift v1.0.3
>>    - Cordova PushPlugin v2.0.1
>>
>> Any suggestions / pointers would be greatly appreciated! Thanks!
>>
>> -Miles
>>
>> _______________________________________________
>> 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
>



-- 
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/20150811/c90e9a78/attachment.html 

From matzew at apache.org  Tue Aug 11 07:01:12 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 11 Aug 2015 13:01:12 +0200
Subject: [aerogear-dev] windows 10
In-Reply-To: <CAO2B-fbJY1orypMfgo8dy5E9r=LUwAmFHumgAo2nEYYhmpZDRA@mail.gmail.com>
References: <CAO2B-fbJY1orypMfgo8dy5E9r=LUwAmFHumgAo2nEYYhmpZDRA@mail.gmail.com>
Message-ID: <CAAg5f2QSxO9Ug7tQ3VUytcB6Vjc3+t+tOgY-qFHG41dGD7tVjw@mail.gmail.com>

Awesome!

Wanna write a little post for aerogear.org on this subject ?

On Fri, Aug 7, 2015 at 1:46 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi,
>
> After some tests we've released windows 10 support for
> aerogear-windows-push and aerogear-windows-oauth2 both have been published
> on nuget. With oauth2 that used to be only wnidows phone the upgrade to
> windows 10 make it possible to use it on tablet and desktop, just like
> push.
>
> Hope you like it
>
> --
> Cheers,
>        Erik Jan
>
> _______________________________________________
> 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/20150811/8efc1ffa/attachment.html 

From matzew at apache.org  Tue Aug 11 07:06:20 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 11 Aug 2015 13:06:20 +0200
Subject: [aerogear-dev] Updated Node Sender released
In-Reply-To: <CALD3Fd0+E3JEoS6iJmsov3ug4QJ4-6AbKDuCAX6tAq2p4Dm6Eg@mail.gmail.com>
References: <CALD3Fd0+E3JEoS6iJmsov3ug4QJ4-6AbKDuCAX6tAq2p4Dm6Eg@mail.gmail.com>
Message-ID: <CAAg5f2TCKOWPXABE+XrO+UViFM7f8fdTtRKbajX3fFSRDu9o9Q@mail.gmail.com>

yay!

On Mon, Aug 10, 2015 at 3:30 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> Now that the 1.1.0.Final release is about to be released of the
> UnifiedPush Server, i've released the 0.8.0 version of the Node Sender.
>
> This includes the new message format that the UPS needs.
>
> you can get it in all the normal ways
>
> _______________________________________________
> 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/20150811/5da718c4/attachment.html 

From matzew at apache.org  Tue Aug 11 07:06:38 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 11 Aug 2015 13:06:38 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.0.Final
In-Reply-To: <CAD_dpu2N8GvrZwx9GJO4NYwA4r7=yE-Dt3LX5z+JdVRGs8vfdw@mail.gmail.com>
References: <CAD_dpu2N8GvrZwx9GJO4NYwA4r7=yE-Dt3LX5z+JdVRGs8vfdw@mail.gmail.com>
Message-ID: <CAAg5f2RMi3Tbbz521hJq4-UsMRQp84y5MeqZKpW08aLyqG92ZA@mail.gmail.com>

looking...

On Fri, Aug 7, 2015 at 3:48 PM, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> Hi team,
>
> I'm happy to announce that UPS 1.1.0 Final has been staged.
>
> Please test the staged release :
>
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6277
>
> On Wednesday I'd like to press the button to release it to the wild.
>
> Sebi
>
> ps : the openshift update will follow
>
>
>
> _______________________________________________
> 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/20150811/ccf77dd5/attachment.html 

From matzew at apache.org  Tue Aug 11 07:12:26 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 11 Aug 2015 13:12:26 +0200
Subject: [aerogear-dev] UPS Categories going forward
In-Reply-To: <CAO2B-faH=U1DPRbvkAJYMteeQH1tQnJ7w8L-k+5_c_d13Y0vjg@mail.gmail.com>
References: <CAEQz2CtXQaXpQRbbc0KsZ6ZLXPF-fkXROphA-5Sb5tR7ue6FVg@mail.gmail.com>
	<CAD_dpu3dyOE1_VAz9MZMWaEOavRo7CCxJgHCDjP20CYdRNE-3A@mail.gmail.com>
	<CAEQz2CtqaHdzKwtEN4K3sNn1JOyJ9JNUD4W5aDAFAZO1WhwCwA@mail.gmail.com>
	<CAO2B-faH=U1DPRbvkAJYMteeQH1tQnJ7w8L-k+5_c_d13Y0vjg@mail.gmail.com>
Message-ID: <CAAg5f2TwGNTW7tkr5RgONVTyBaXUc8p1_U2o_R=x8Sb1YGR=4w@mail.gmail.com>

On Thu, Aug 6, 2015 at 4:30 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> +1 on this I think it's very useful to have a specific listener per
> topic/category like I said before ;)
>

agreed


>
> -1 on re-using register, even though that already works, I would like a
> new endpoint to make it's intent more clear also, some clients need to
> store things locally to be able to call register multiple times (iOS and
> windows). But we could do it as an initial version.
>

agreed! We even have a ticket for this new endpoint, that just updates the
metadata:
https://issues.jboss.org/browse/AGPUSH-1399


>
> On Thu, Aug 6, 2015 at 4:23 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>>
>>
>> On Thu, Aug 6, 2015 at 10:14 AM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>>
>>>
>>> On Thu, Aug 6, 2015 at 3:58 PM, Summers Pittman <supittma at redhat.com>
>>> wrote:
>>>
>>>> Y'all,
>>>>
>>>> Since I now have a GCM Topic PR up I figure it is time to revisit
>>>> beefing up categories a bit.
>>>>
>>>> Before we discussed enhancing the server and client APIs so one could
>>>> subscribe and unsubscribe to topics without unregistering and
>>>> reregistering.  This will require a new endpoint on UPS and new code in all
>>>> the libraries
>>>>
>>>
>>> I agree we need a  PUT /device/metadata (or smt like that) even if today
>>> we support updating of existing installations; if you register an existing
>>> device, it will just update its metadata
>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/impl/ClientInstallationServiceImpl.java#L69-L80
>>>
>>>
>>>
>>
>> Oooo.  So just spamming register is an option. Thanks!
>>
>>
>>>
>>>> We also discussed adding the ability to "route" messages to specific
>>>> handlers based on what category the message was sent to.  This will require
>>>> adding a field to all push messages that don't use GCM topics.  It will
>>>> also require updates on the client code.
>>>>
>>> Can you elaborate a bit on that or point me to previous  discussions ?
>>>
>> I was thinking of edewit's comment:
>>
>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-topic-messaging-enhancements-AGDROID-470-td11997.html
>>
>>
>>>
>>>> As an aside there is also GCM support on iOS, but it is much more
>>>> complicated to set up.
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Cheers,
>        Erik Jan
>
> _______________________________________________
> 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/20150811/d2e6f19a/attachment-0001.html 

From matzew at apache.org  Tue Aug 11 07:12:40 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 11 Aug 2015 13:12:40 +0200
Subject: [aerogear-dev] UPS Categories going forward
In-Reply-To: <CAO2B-fbRYhhJfppTvUHB+rGfOXUQ7-C1gBjQDdrg5XWcAbhuBg@mail.gmail.com>
References: <CAEQz2CtXQaXpQRbbc0KsZ6ZLXPF-fkXROphA-5Sb5tR7ue6FVg@mail.gmail.com>
	<CAD_dpu3dyOE1_VAz9MZMWaEOavRo7CCxJgHCDjP20CYdRNE-3A@mail.gmail.com>
	<CAEQz2CtqaHdzKwtEN4K3sNn1JOyJ9JNUD4W5aDAFAZO1WhwCwA@mail.gmail.com>
	<CAO2B-faH=U1DPRbvkAJYMteeQH1tQnJ7w8L-k+5_c_d13Y0vjg@mail.gmail.com>
	<CAD_dpu2SWM8432bMY-4vAHbo-BEiRk5HGOVTLT-4RKXbiQVJjQ@mail.gmail.com>
	<CAO2B-fbRYhhJfppTvUHB+rGfOXUQ7-C1gBjQDdrg5XWcAbhuBg@mail.gmail.com>
Message-ID: <CAAg5f2RR0W4LmgOFSxvtTVhSq0R9X+042qjd7nYA-yFL5PqCHw@mail.gmail.com>

On Thu, Aug 6, 2015 at 4:43 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Sure you can do it yourself, but now that GCM has topics and we add
> support for it in the true nature of unifying it's good to have support for
> that on the other platforms as well
>
yep

>
> On Thu, Aug 6, 2015 at 4:38 PM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> Okay I see, I like the idea as well even the developer could already
>> implement this himself (he just pass the categories in the payload and in
>> the client he implements the routing).
>> Do we have a jira for this ?
>>
>> On Thu, Aug 6, 2015 at 4:30 PM, Erik Jan de Wit <edewit at redhat.com>
>> wrote:
>>
>>> +1 on this I think it's very useful to have a specific listener per
>>> topic/category like I said before ;)
>>>
>>> -1 on re-using register, even though that already works, I would like a
>>> new endpoint to make it's intent more clear also, some clients need to
>>> store things locally to be able to call register multiple times (iOS and
>>> windows). But we could do it as an initial version.
>>>
>>> On Thu, Aug 6, 2015 at 4:23 PM, Summers Pittman <supittma at redhat.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Thu, Aug 6, 2015 at 10:14 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Thu, Aug 6, 2015 at 3:58 PM, Summers Pittman <supittma at redhat.com>
>>>>> wrote:
>>>>>
>>>>>> Y'all,
>>>>>>
>>>>>> Since I now have a GCM Topic PR up I figure it is time to revisit
>>>>>> beefing up categories a bit.
>>>>>>
>>>>>> Before we discussed enhancing the server and client APIs so one could
>>>>>> subscribe and unsubscribe to topics without unregistering and
>>>>>> reregistering.  This will require a new endpoint on UPS and new code in all
>>>>>> the libraries
>>>>>>
>>>>>
>>>>> I agree we need a  PUT /device/metadata (or smt like that) even if
>>>>> today we support updating of existing installations; if you register an
>>>>> existing device, it will just update its metadata
>>>>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/service/src/main/java/org/jboss/aerogear/unifiedpush/service/impl/ClientInstallationServiceImpl.java#L69-L80
>>>>>
>>>>>
>>>>>
>>>>
>>>> Oooo.  So just spamming register is an option. Thanks!
>>>>
>>>>
>>>>>
>>>>>> We also discussed adding the ability to "route" messages to specific
>>>>>> handlers based on what category the message was sent to.  This will require
>>>>>> adding a field to all push messages that don't use GCM topics.  It will
>>>>>> also require updates on the client code.
>>>>>>
>>>>> Can you elaborate a bit on that or point me to previous  discussions ?
>>>>>
>>>>>
>>>> I was thinking of edewit's comment:
>>>>
>>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-topic-messaging-enhancements-AGDROID-470-td11997.html
>>>>
>>>>
>>>>>
>>>>>> As an aside there is also GCM support on iOS, but it is much more
>>>>>> complicated to set up.
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Cheers,
>>>        Erik Jan
>>>
>>> _______________________________________________
>>> 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
>>
>
>
>
> --
> Cheers,
>        Erik Jan
>
> _______________________________________________
> 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/20150811/fa550f08/attachment.html 

From matzew at apache.org  Tue Aug 11 07:13:38 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 11 Aug 2015 13:13:38 +0200
Subject: [aerogear-dev] UPS Categories going forward
In-Reply-To: <CAEQz2CtXQaXpQRbbc0KsZ6ZLXPF-fkXROphA-5Sb5tR7ue6FVg@mail.gmail.com>
References: <CAEQz2CtXQaXpQRbbc0KsZ6ZLXPF-fkXROphA-5Sb5tR7ue6FVg@mail.gmail.com>
Message-ID: <CAAg5f2QqyNfLVRfeNOkdqqz=xHfDyZStockQQkvdHavDUFJkuQ@mail.gmail.com>

On Thu, Aug 6, 2015 at 3:58 PM, Summers Pittman <supittma at redhat.com> wrote:

> Y'all,
>
> Since I now have a GCM Topic PR up I figure it is time to revisit beefing
> up categories a bit.
>
> Before we discussed enhancing the server and client APIs so one could
> subscribe and unsubscribe to topics without unregistering and
> reregistering.  This will require a new endpoint on UPS and new code in all
> the libraries
>
> We also discussed adding the ability to "route" messages to specific
> handlers based on what category the message was sent to.  This will require
> adding a field to all push messages that don't use GCM topics.  It will
> also require updates on the client code.
>
> As an aside there is also GCM support on iOS, but it is much more
> complicated to set up.
>

yes, it's nice - but I have reservations against this too. I guess it would
translate into a separate variant type GCM-APNs, since not all really want
this ;-) But it's something we could do for 2.x


>
> _______________________________________________
> 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/20150811/82a22093/attachment.html 

From matzew at apache.org  Tue Aug 11 07:14:28 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 11 Aug 2015 13:14:28 +0200
Subject: [aerogear-dev] GCM Topic Messaging in UPS
In-Reply-To: <CAEQz2CtzUwaRDeHYXEd++cRYAJ+MxdRDzZqbfRPZTSBtK+u77g@mail.gmail.com>
References: <CAEQz2CtzUwaRDeHYXEd++cRYAJ+MxdRDzZqbfRPZTSBtK+u77g@mail.gmail.com>
Message-ID: <CAAg5f2QC3iqdNXk-DE223rq+J-WT8V-_O+E3hAPxfY=_zv=KJQ@mail.gmail.com>

cool stuff!

On Thu, Aug 6, 2015 at 3:42 PM, Summers Pittman <supittma at redhat.com> wrote:

>
> Here's a video demo :
> https://www.youtube.com/watch?v=s7tXcbua_sM&feature=youtu.be
>
> Here's the PRs :
>  * UPS : https://github.com/aerogear/aerogear-unifiedpush-server/pull/626
>  * AGDROID : https://github.com/aerogear/aerogear-android-push/pull/50
>
> I would link the JIRAs but I closed those tabs ;)
>
> _______________________________________________
> 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/20150811/936cd498/attachment.html 

From supittma at redhat.com  Tue Aug 11 09:48:59 2015
From: supittma at redhat.com (Summers Pittman)
Date: Tue, 11 Aug 2015 09:48:59 -0400
Subject: [aerogear-dev] UPS 1.2, GCM 3.0 Topics,
	and Google's rest-client updates
In-Reply-To: <CAPXQee4xSeZdwKDG0oiKrTDGV=2eDeczzdaA5WCefWBn8fjYAw@mail.gmail.com>
References: <CAEQz2CvU1FJMY9=p0Fa1rBRo-fsJ=4U5vmZJjkFcWfaHu7+Hfg@mail.gmail.com>
	<CAPXQee6GAL=HrpH4W7En-4ki1HMf_-3c-FAHFaTH1ceO=TG9vg@mail.gmail.com>
	<CAEQz2CuF3kVnoF9HsJ7MCN8pvSE5bm=eDsQgaix4fxS+OnRgLg@mail.gmail.com>
	<CAPXQee4xSeZdwKDG0oiKrTDGV=2eDeczzdaA5WCefWBn8fjYAw@mail.gmail.com>
Message-ID: <CAEQz2CtQRHKfLsMGbq78zCw3nxL0CEuqHfFT7eEPNVOWtQ4KzQ@mail.gmail.com>

On Tue, Aug 4, 2015 at 3:36 PM, Karel Piwko <kpiwko at redhat.com> wrote:

> I mean
> https://github.com/google/gcm/blob/master/client-libraries/java/rest-client/src/com/google/android/gcm/server/Constants.java#L27
> which makes impossible to replace GCM backend with mocked backend for
> testing purposes. Other messaging provider libraries allow that.
>
>
So basically Karel you are saying that their library is unsuited for our
applications without some serious modification?

Right now in the Topics PR I have a branched, snipped, and (slightly)
refactored maven version.  Feel free to give you feedback there.

Karel
>
> On Mon, Aug 3, 2015 at 6:46 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>>
>>
>> On Mon, Aug 3, 2015 at 10:33 AM, Karel Piwko <kpiwko at redhat.com> wrote:
>>
>>> Hello Summers,
>>>
>>> my concern would be that this repo is Ant based and not available in
>>> Maven Central. So a fork would indeed be needed. Other problem is that the
>>> lib does not support supplying backend server location -
>>>
>> What do you mean?
>>
>>> but this is something a PR can fix. In the past, I believe that we
>>> evaluated this library as an option as well
>>> https://github.com/phonedeck/gcm4j
>>>
>>> Cheers,
>>>
>>> Karel
>>>
>>>
>>> On Fri, Jul 31, 2015 at 5:04 PM, Summers Pittman <supittma at redhat.com>
>>> wrote:
>>>
>>>> Guys and gals,
>>>>
>>>> UPS is currently using a fork of Google's rest-client sample to
>>>> communicate with Google's servers (See the previous thread UPS and
>>>> com.ganyo:gcm-server for details**).  This is an outdated fork from
>>>> https://github.com/google/gcm.
>>>>
>>>> It is in fact very outdated.  The rest client code, Message and Builder
>>>> objects, Constant fields, and Sender code don't support all of the
>>>> fields/errors/etc needed for GCM topics messaging.  Additionally it uses a
>>>> deprecated field in a few places.  I've filed two* issues*** in the gcm
>>>> project to reach out and begin work with them to resolve this in a more
>>>> sane way.  In the meanwhile we will probably have to patch and support our
>>>> own fork of the library.
>>>>
>>>> Thoughts, comments, tomatoes?
>>>>
>>>> PS, this will probably bump XMPP support from aerogear-android-push 3.0
>>>> and UPS 1.2.  Please let me know if it should and i will pull those from
>>>> the JIRA epics and we can reschedule them.
>>>>
>>>> Summers
>>>>
>>>> * https://github.com/google/gcm/issues/84
>>>> *** https://github.com/google/gcm/issues/85
>>>> **
>>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UPS-and-com-ganyo-gcm-server-td12015.html
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> 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/20150811/52b39e18/attachment-0001.html 

From edewit at redhat.com  Tue Aug 11 11:17:57 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 11 Aug 2015 17:17:57 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.0.Final
In-Reply-To: <CAAg5f2RMi3Tbbz521hJq4-UsMRQp84y5MeqZKpW08aLyqG92ZA@mail.gmail.com>
References: <CAD_dpu2N8GvrZwx9GJO4NYwA4r7=yE-Dt3LX5z+JdVRGs8vfdw@mail.gmail.com>
	<CAAg5f2RMi3Tbbz521hJq4-UsMRQp84y5MeqZKpW08aLyqG92ZA@mail.gmail.com>
Message-ID: <CAO2B-faAcmra1pFUgj-zPxfC-vxVzvsVpYMO9WpxT1ihY5R2sQ@mail.gmail.com>

I found these issues:


   1. AGPUSH-1492 <https://issues.jboss.org/browse/AGPUSH-1492> Deleting an
   Application leaves installations
   2.
      1.
         1. AGPUSH-1491 <https://issues.jboss.org/browse/AGPUSH-1491> Android
         doesn't show installations


On Tue, Aug 11, 2015 at 1:06 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> looking...
>
> On Fri, Aug 7, 2015 at 3:48 PM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> Hi team,
>>
>> I'm happy to announce that UPS 1.1.0 Final has been staged.
>>
>> Please test the staged release :
>>
>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6277
>>
>> On Wednesday I'd like to press the button to release it to the wild.
>>
>> Sebi
>>
>> ps : the openshift update will follow
>>
>>
>>
>> _______________________________________________
>> 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/20150811/0c0e3fc0/attachment.html 

From supittma at redhat.com  Tue Aug 11 12:59:11 2015
From: supittma at redhat.com (Summers Pittman)
Date: Tue, 11 Aug 2015 12:59:11 -0400
Subject: [aerogear-dev] GCM Topics feature branch
Message-ID: <CAEQz2CtaRJyZN--AB2tTZeFxfbZcOQJnYdn-s65D0SnPB-EVOg@mail.gmail.com>

So it looks like the work for properly supporting topics is going to grow.
So far we have identified two areas for improvement already :
 * lfryc and I met this afternoon and discussed how to handle topic
failures where calling back to registrationIds is appropriate.  He has some
refactors he wants to make.
 * Last night on the -users list a community member brought up some use
case we have to consider as well.  Specifically around how `alias` and
`deviceType` interact with topics.

In the spirit of keeping the PRs manageable, I propose we create a feature
branches for topics in aerogear/aerogear-unifiedpush-server and
aerogear/aerogear-android-push.

Barring strong opinions against this, I will create these branches and move
my PRs appropriately.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150811/ee46d92a/attachment.html 

From dpassos at redhat.com  Tue Aug 11 13:06:11 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Tue, 11 Aug 2015 14:06:11 -0300
Subject: [aerogear-dev] GCM Topics feature branch
In-Reply-To: <CAEQz2CtaRJyZN--AB2tTZeFxfbZcOQJnYdn-s65D0SnPB-EVOg@mail.gmail.com>
References: <CAEQz2CtaRJyZN--AB2tTZeFxfbZcOQJnYdn-s65D0SnPB-EVOg@mail.gmail.com>
Message-ID: <CADF=h2uQ_PCwjgFABsmXk6VHWiVOyNPDKTSFU8RB0XAsU7HDGw@mail.gmail.com>

+9001 I like use branch for WIP

On Tue, Aug 11, 2015 at 1:59 PM, Summers Pittman <supittma at redhat.com>
wrote:

> So it looks like the work for properly supporting topics is going to
> grow.  So far we have identified two areas for improvement already :
>  * lfryc and I met this afternoon and discussed how to handle topic
> failures where calling back to registrationIds is appropriate.  He has some
> refactors he wants to make.
>  * Last night on the -users list a community member brought up some use
> case we have to consider as well.  Specifically around how `alias` and
> `deviceType` interact with topics.
>
> In the spirit of keeping the PRs manageable, I propose we create a feature
> branches for topics in aerogear/aerogear-unifiedpush-server and
> aerogear/aerogear-android-push.
>
> Barring strong opinions against this, I will create these branches and
> move my PRs appropriately.
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



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

From lukas.fryc at gmail.com  Tue Aug 11 15:48:14 2015
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Tue, 11 Aug 2015 21:48:14 +0200
Subject: [aerogear-dev] GCM Topics feature branch
In-Reply-To: <CADF=h2uQ_PCwjgFABsmXk6VHWiVOyNPDKTSFU8RB0XAsU7HDGw@mail.gmail.com>
References: <CAEQz2CtaRJyZN--AB2tTZeFxfbZcOQJnYdn-s65D0SnPB-EVOg@mail.gmail.com>
	<CADF=h2uQ_PCwjgFABsmXk6VHWiVOyNPDKTSFU8RB0XAsU7HDGw@mail.gmail.com>
Message-ID: <CAEroY35o=a7pBV2bVPF3TAfcjTFfrdB+6+0WXvQ1if0-T_8n3Q@mail.gmail.com>

+1 let's work on it in a branch

On Tue, Aug 11, 2015 at 7:06 PM, Daniel Passos <dpassos at redhat.com> wrote:

> +9001 I like use branch for WIP
>
> On Tue, Aug 11, 2015 at 1:59 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>> So it looks like the work for properly supporting topics is going to
>> grow.  So far we have identified two areas for improvement already :
>>  * lfryc and I met this afternoon and discussed how to handle topic
>> failures where calling back to registrationIds is appropriate.  He has some
>> refactors he wants to make.
>>  * Last night on the -users list a community member brought up some use
>> case we have to consider as well.  Specifically around how `alias` and
>> `deviceType` interact with topics.
>>
>> In the spirit of keeping the PRs manageable, I propose we create a
>> feature branches for topics in aerogear/aerogear-unifiedpush-server and
>> aerogear/aerogear-android-push.
>>
>> Barring strong opinions against this, I will create these branches and
>> move my PRs appropriately.
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> -- Passos
>
> _______________________________________________
> 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/20150811/9c6c7abe/attachment.html 

From matzew at apache.org  Tue Aug 11 16:39:33 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 11 Aug 2015 22:39:33 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.0.Final
In-Reply-To: <CAO2B-faAcmra1pFUgj-zPxfC-vxVzvsVpYMO9WpxT1ihY5R2sQ@mail.gmail.com>
References: <CAD_dpu2N8GvrZwx9GJO4NYwA4r7=yE-Dt3LX5z+JdVRGs8vfdw@mail.gmail.com>
	<CAAg5f2RMi3Tbbz521hJq4-UsMRQp84y5MeqZKpW08aLyqG92ZA@mail.gmail.com>
	<CAO2B-faAcmra1pFUgj-zPxfC-vxVzvsVpYMO9WpxT1ihY5R2sQ@mail.gmail.com>
Message-ID: <CAAg5f2TtCj-zv-Cu1W3zusX3XcaXbwTWdRA-AuJf_c_bVQ1YuQ@mail.gmail.com>

I think this is aldo worth to be included to 1.1.0.Final

On Tuesday, August 11, 2015, Erik Jan de Wit <edewit at redhat.com> wrote:

> I found these issues:
>
>
>    1. AGPUSH-1492 <https://issues.jboss.org/browse/AGPUSH-1492> Deleting
>    an Application leaves installations
>    2.
>       1.
>          1. AGPUSH-1491 <https://issues.jboss.org/browse/AGPUSH-1491> Android
>          doesn't show installations
>
>
> On Tue, Aug 11, 2015 at 1:06 PM, Matthias Wessendorf <matzew at apache.org
> <javascript:_e(%7B%7D,'cvml','matzew at apache.org');>> wrote:
>
>> looking...
>>
>> On Fri, Aug 7, 2015 at 3:48 PM, Sebastien Blanc <scm.blanc at gmail.com
>> <javascript:_e(%7B%7D,'cvml','scm.blanc at gmail.com');>> wrote:
>>
>>> Hi team,
>>>
>>> I'm happy to announce that UPS 1.1.0 Final has been staged.
>>>
>>> Please test the staged release :
>>>
>>>
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6277
>>>
>>> On Wednesday I'd like to press the button to release it to the wild.
>>>
>>> Sebi
>>>
>>> ps : the openshift update will follow
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> <javascript:_e(%7B%7D,'cvml','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
>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Cheers,
>        Erik Jan
>


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

From matzew at apache.org  Wed Aug 12 02:50:39 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 12 Aug 2015 08:50:39 +0200
Subject: [aerogear-dev] GCM Topics feature branch
In-Reply-To: <CAEroY35o=a7pBV2bVPF3TAfcjTFfrdB+6+0WXvQ1if0-T_8n3Q@mail.gmail.com>
References: <CAEQz2CtaRJyZN--AB2tTZeFxfbZcOQJnYdn-s65D0SnPB-EVOg@mail.gmail.com>
	<CADF=h2uQ_PCwjgFABsmXk6VHWiVOyNPDKTSFU8RB0XAsU7HDGw@mail.gmail.com>
	<CAEroY35o=a7pBV2bVPF3TAfcjTFfrdB+6+0WXvQ1if0-T_8n3Q@mail.gmail.com>
Message-ID: <CAAg5f2RXHo7ZqgJba=yKBJ+X6eArbFdZu210e3uJ2078iKaKGw@mail.gmail.com>

+1

On Tue, Aug 11, 2015 at 9:48 PM, Luk?? Fry? <lukas.fryc at gmail.com> wrote:

> +1 let's work on it in a branch
>
> On Tue, Aug 11, 2015 at 7:06 PM, Daniel Passos <dpassos at redhat.com> wrote:
>
>> +9001 I like use branch for WIP
>>
>> On Tue, Aug 11, 2015 at 1:59 PM, Summers Pittman <supittma at redhat.com>
>> wrote:
>>
>>> So it looks like the work for properly supporting topics is going to
>>> grow.  So far we have identified two areas for improvement already :
>>>  * lfryc and I met this afternoon and discussed how to handle topic
>>> failures where calling back to registrationIds is appropriate.  He has some
>>> refactors he wants to make.
>>>  * Last night on the -users list a community member brought up some use
>>> case we have to consider as well.  Specifically around how `alias` and
>>> `deviceType` interact with topics.
>>>
>>> In the spirit of keeping the PRs manageable, I propose we create a
>>> feature branches for topics in aerogear/aerogear-unifiedpush-server and
>>> aerogear/aerogear-android-push.
>>>
>>> Barring strong opinions against this, I will create these branches and
>>> move my PRs appropriately.
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> -- Passos
>>
>> _______________________________________________
>> 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/20150812/8855b792/attachment.html 

From scm.blanc at gmail.com  Wed Aug 12 02:52:29 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 12 Aug 2015 08:52:29 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.0.Final
In-Reply-To: <CAAg5f2TtCj-zv-Cu1W3zusX3XcaXbwTWdRA-AuJf_c_bVQ1YuQ@mail.gmail.com>
References: <CAD_dpu2N8GvrZwx9GJO4NYwA4r7=yE-Dt3LX5z+JdVRGs8vfdw@mail.gmail.com>
	<CAAg5f2RMi3Tbbz521hJq4-UsMRQp84y5MeqZKpW08aLyqG92ZA@mail.gmail.com>
	<CAO2B-faAcmra1pFUgj-zPxfC-vxVzvsVpYMO9WpxT1ihY5R2sQ@mail.gmail.com>
	<CAAg5f2TtCj-zv-Cu1W3zusX3XcaXbwTWdRA-AuJf_c_bVQ1YuQ@mail.gmail.com>
Message-ID: <CAD_dpu3O8jZnndF_2B_MTNzg38QEJAVL2BFmaSo9OXjo9uJKcA@mail.gmail.com>

Yes, I will discard the current staged release.
Thanks Erik for reporting these issues.



On Tue, Aug 11, 2015 at 10:39 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> I think this is aldo worth to be included to 1.1.0.Final
>
>
> On Tuesday, August 11, 2015, Erik Jan de Wit <edewit at redhat.com> wrote:
>
>> I found these issues:
>>
>>
>>    1. AGPUSH-1492 <https://issues.jboss.org/browse/AGPUSH-1492> Deleting
>>    an Application leaves installations
>>    2.
>>       1.
>>          1. AGPUSH-1491 <https://issues.jboss.org/browse/AGPUSH-1491> Android
>>          doesn't show installations
>>
>>
>> On Tue, Aug 11, 2015 at 1:06 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> looking...
>>>
>>> On Fri, Aug 7, 2015 at 3:48 PM, Sebastien Blanc <scm.blanc at gmail.com>
>>> wrote:
>>>
>>>> Hi team,
>>>>
>>>> I'm happy to announce that UPS 1.1.0 Final has been staged.
>>>>
>>>> Please test the staged release :
>>>>
>>>>
>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6277
>>>>
>>>> On Wednesday I'd like to press the button to release it to the wild.
>>>>
>>>> Sebi
>>>>
>>>> ps : the openshift update will follow
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>
>
>
> --
> Sent from Gmail Mobile
>
> _______________________________________________
> 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/20150812/163425c3/attachment.html 

From omatskiv at redhat.com  Wed Aug 12 06:37:11 2015
From: omatskiv at redhat.com (Oleg Matskiv)
Date: Wed, 12 Aug 2015 12:37:11 +0200
Subject: [aerogear-dev] UPS Migrator error (1.1.0.Final)
Message-ID: <CALimhXp7kzjL3vCFfYs8Fc8NmdNn2h2BdQbO8mR-byrXQhi90A@mail.gmail.com>

Hi,
can somebody who worked on UPS migrator recently, check if it deals with
recent database changes (e.g.
https://github.com/aerogear/aerogear-unifiedpush-server/commit/bbe1c0e80a4a5295a3c7cefe66f5e8cc07da66be#diff-23e531d12489411024ea5c379be1d178R70
).

I have run into error when running integration test with migrator run
(liquibase.exception.DatabaseException:
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Key column
'variantInformations_id' doesn't exist in table).

Thanks for any help.

-- 
Oleg Matskiv
Mobile QE Intern
omatskiv at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150812/89657844/attachment.html 

From lukas at fryc.eu  Wed Aug 12 09:22:05 2015
From: lukas at fryc.eu (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Wed, 12 Aug 2015 15:22:05 +0200
Subject: [aerogear-dev] GCM Topics - split into two sender implementations?
Message-ID: <CAEroY37VCG2VxuyjYTZrbhcoq1QJm2zMAzaDuPPeXkzcdoBVTg@mail.gmail.com>

Hi guys,

/wrt the GCM Topics support PR
https://github.com/aerogear/aerogear-unifiedpush-server/pull/626

me and summersp have discussed how JMS should be used to route messages.


Current implementation loads tokens and conditionally sends either message
with registration IDs or topics.

There are two things yet to be solved:

   -  topics can be used up to 1 million registrations, otherwise you have
   to fall back to enumerating registration IDs
   - implementation with one sender (GCMPushNotificationSender) is
   suboptimal
      - the utilization of the topics can be increased by prioritizing
      topic message sending first (covering multiple, potentially thousands
      registrations)
      - followed by sending registration IDs out


That's why I suggested to split implementation to two JMS queues talking to
two sender impls (e.g. GCMTopicSender and GCMRegistrationIdsSender).

   - first we send out topic based messages (for efficiency)
   - we collect those topics that fail and resend them for processing as
   registration IDs (fail over)
      - registration ids sending can start in parallel, but it can't end
      until we sent out all topics

Additionally we get an ability to configure these two message routes
individually on the JMS level (better utilization, transact-ability, fail
over).


What do you think?


Cheers,

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

From matzew at apache.org  Wed Aug 12 09:31:27 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 12 Aug 2015 15:31:27 +0200
Subject: [aerogear-dev] GCM Topics - split into two sender
	implementations?
In-Reply-To: <CAEroY37VCG2VxuyjYTZrbhcoq1QJm2zMAzaDuPPeXkzcdoBVTg@mail.gmail.com>
References: <CAEroY37VCG2VxuyjYTZrbhcoq1QJm2zMAzaDuPPeXkzcdoBVTg@mail.gmail.com>
Message-ID: <CAAg5f2S77Vr3qTpABHDLBDtFhuyqpDh+qxGgrfrPfEYVDAaOCg@mail.gmail.com>

On Wed, Aug 12, 2015 at 3:22 PM, Luk?? Fry? <lukas at fryc.eu> wrote:

> Hi guys,
>
> /wrt the GCM Topics support PR
> https://github.com/aerogear/aerogear-unifiedpush-server/pull/626
>
> me and summersp have discussed how JMS should be used to route messages.
>
>
> Current implementation loads tokens and conditionally sends either message
> with registration IDs or topics.
>
> There are two things yet to be solved:
>
>    -  topics can be used up to 1 million registrations, otherwise you
>    have to fall back to enumerating registration IDs
>    - implementation with one sender (GCMPushNotificationSender) is
>    suboptimal
>       - the utilization of the topics can be increased by prioritizing
>       topic message sending first (covering multiple, potentially thousands
>       registrations)
>       - followed by sending registration IDs out
>
>
> That's why I suggested to split implementation to two JMS queues talking
> to two sender impls (e.g. GCMTopicSender and GCMRegistrationIdsSender).
>
>    - first we send out topic based messages (for efficiency)
>    - we collect those topics that fail and resend them for processing as
>    registration IDs (fail over)
>       - registration ids sending can start in parallel, but it can't end
>       until we sent out all topics
>
>
I agree that we need a slip here - but does it (GCM) really work like that
?
I was more thinking/guess that we have to do the math and keep the device
nr. per topic - wondering now, summers, what actually happens if device
1.000.001 registers w/ the topic? Does GCM fail the device ?


> Additionally we get an ability to configure these two message routes
> individually on the JMS level (better utilization, transact-ability, fail
> over).
>

but generally, I think these are two completely different cases, therefore
we need to different senders

>
>
> What do you think?
>
>
> Cheers,
>
> ~ Lukas
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From supittma at redhat.com  Wed Aug 12 09:35:08 2015
From: supittma at redhat.com (Summers Pittman)
Date: Wed, 12 Aug 2015 09:35:08 -0400
Subject: [aerogear-dev] GCM Topics - split into two sender
	implementations?
In-Reply-To: <CAEroY37VCG2VxuyjYTZrbhcoq1QJm2zMAzaDuPPeXkzcdoBVTg@mail.gmail.com>
References: <CAEroY37VCG2VxuyjYTZrbhcoq1QJm2zMAzaDuPPeXkzcdoBVTg@mail.gmail.com>
Message-ID: <CAEQz2CsFCU7vSMsTWmfaW56UfhJhjsVwSP5CEki84BFxGhX-_A@mail.gmail.com>

On Wed, Aug 12, 2015 at 9:22 AM, Luk?? Fry? <lukas at fryc.eu> wrote:

> Hi guys,
>
> /wrt the GCM Topics support PR
> https://github.com/aerogear/aerogear-unifiedpush-server/pull/626
>
> me and summersp have discussed how JMS should be used to route messages.
>
>
> Current implementation loads tokens and conditionally sends either message
> with registration IDs or topics.
>
> There are two things yet to be solved:
>
>    -  topics can be used up to 1 million registrations, otherwise you
>    have to fall back to enumerating registration IDs
>    - implementation with one sender (GCMPushNotificationSender) is
>    suboptimal
>       - the utilization of the topics can be increased by prioritizing
>       topic message sending first (covering multiple, potentially thousands
>       registrations)
>       - followed by sending registration IDs out
>
>
> That's why I suggested to split implementation to two JMS queues talking
> to two sender impls (e.g. GCMTopicSender and GCMRegistrationIdsSender).
>
>    - first we send out topic based messages (for efficiency)
>    - we collect those topics that fail and resend them for processing as
>    registration IDs (fail over)
>       - registration ids sending can start in parallel, but it can't end
>       until we sent out all topics
>
> Additionally we get an ability to configure these two message routes
> individually on the JMS level (better utilization, transact-ability, fail
> over).
>
>
> What do you think?
>
Since we discussed this yesterday I am of course +1 :-p

>
>
> Cheers,
>
> ~ Lukas
>
> _______________________________________________
> 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/20150812/197e9d49/attachment.html 

From supittma at redhat.com  Wed Aug 12 09:36:45 2015
From: supittma at redhat.com (Summers Pittman)
Date: Wed, 12 Aug 2015 09:36:45 -0400
Subject: [aerogear-dev] GCM Topics - split into two sender
	implementations?
In-Reply-To: <CAAg5f2S77Vr3qTpABHDLBDtFhuyqpDh+qxGgrfrPfEYVDAaOCg@mail.gmail.com>
References: <CAEroY37VCG2VxuyjYTZrbhcoq1QJm2zMAzaDuPPeXkzcdoBVTg@mail.gmail.com>
	<CAAg5f2S77Vr3qTpABHDLBDtFhuyqpDh+qxGgrfrPfEYVDAaOCg@mail.gmail.com>
Message-ID: <CAEQz2CvideoJ=APdN3uZbNqia63A-tzAYMOYmRMOd_RBAdHEJQ@mail.gmail.com>

On Wed, Aug 12, 2015 at 9:31 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Wed, Aug 12, 2015 at 3:22 PM, Luk?? Fry? <lukas at fryc.eu> wrote:
>
>> Hi guys,
>>
>> /wrt the GCM Topics support PR
>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/626
>>
>> me and summersp have discussed how JMS should be used to route messages.
>>
>>
>> Current implementation loads tokens and conditionally sends either
>> message with registration IDs or topics.
>>
>> There are two things yet to be solved:
>>
>>    -  topics can be used up to 1 million registrations, otherwise you
>>    have to fall back to enumerating registration IDs
>>    - implementation with one sender (GCMPushNotificationSender) is
>>    suboptimal
>>       - the utilization of the topics can be increased by prioritizing
>>       topic message sending first (covering multiple, potentially thousands
>>       registrations)
>>       - followed by sending registration IDs out
>>
>>
>> That's why I suggested to split implementation to two JMS queues talking
>> to two sender impls (e.g. GCMTopicSender and GCMRegistrationIdsSender).
>>
>>    - first we send out topic based messages (for efficiency)
>>    - we collect those topics that fail and resend them for processing as
>>    registration IDs (fail over)
>>       - registration ids sending can start in parallel, but it can't end
>>       until we sent out all topics
>>
>>
> I agree that we need a slip here - but does it (GCM) really work like that
> ?
> I was more thinking/guess that we have to do the math and keep the device
> nr. per topic - wondering now, summers, what actually happens if device
> 1.000.001 registers w/ the topic? Does GCM fail the device ?
>

As far as Google's docs say, the device will register with GCM but the
topics will fail to send on the server.

Specifically when we send the post to Google we will receive a failure
messages TOO_MANY_DEVICES.  See the GCM Sender in the PR for exact details.


>
>> Additionally we get an ability to configure these two message routes
>> individually on the JMS level (better utilization, transact-ability, fail
>> over).
>>
>
> but generally, I think these are two completely different cases, therefore
> we need to different senders
>
>>
>>
>> What do you think?
>>
>>
>> Cheers,
>>
>> ~ Lukas
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> 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/20150812/df3b239b/attachment.html 

From matzew at apache.org  Wed Aug 12 09:41:34 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 12 Aug 2015 15:41:34 +0200
Subject: [aerogear-dev] GCM Topics - split into two sender
	implementations?
In-Reply-To: <CAEQz2CvideoJ=APdN3uZbNqia63A-tzAYMOYmRMOd_RBAdHEJQ@mail.gmail.com>
References: <CAEroY37VCG2VxuyjYTZrbhcoq1QJm2zMAzaDuPPeXkzcdoBVTg@mail.gmail.com>
	<CAAg5f2S77Vr3qTpABHDLBDtFhuyqpDh+qxGgrfrPfEYVDAaOCg@mail.gmail.com>
	<CAEQz2CvideoJ=APdN3uZbNqia63A-tzAYMOYmRMOd_RBAdHEJQ@mail.gmail.com>
Message-ID: <CAAg5f2RY4xXfY7UiZ_e30it4iVdYR+tiFXWsoMqB+2Zn8RTZJA@mail.gmail.com>

On Wed, Aug 12, 2015 at 3:36 PM, Summers Pittman <supittma at redhat.com>
wrote:

>
>
> On Wed, Aug 12, 2015 at 9:31 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Wed, Aug 12, 2015 at 3:22 PM, Luk?? Fry? <lukas at fryc.eu> wrote:
>>
>>> Hi guys,
>>>
>>> /wrt the GCM Topics support PR
>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/626
>>>
>>> me and summersp have discussed how JMS should be used to route messages.
>>>
>>>
>>> Current implementation loads tokens and conditionally sends either
>>> message with registration IDs or topics.
>>>
>>> There are two things yet to be solved:
>>>
>>>    -  topics can be used up to 1 million registrations, otherwise you
>>>    have to fall back to enumerating registration IDs
>>>    - implementation with one sender (GCMPushNotificationSender) is
>>>    suboptimal
>>>       - the utilization of the topics can be increased by prioritizing
>>>       topic message sending first (covering multiple, potentially thousands
>>>       registrations)
>>>       - followed by sending registration IDs out
>>>
>>>
>>> That's why I suggested to split implementation to two JMS queues talking
>>> to two sender impls (e.g. GCMTopicSender and GCMRegistrationIdsSender).
>>>
>>>    - first we send out topic based messages (for efficiency)
>>>    - we collect those topics that fail and resend them for processing
>>>    as registration IDs (fail over)
>>>       - registration ids sending can start in parallel, but it can't
>>>       end until we sent out all topics
>>>
>>>
>> I agree that we need a slip here - but does it (GCM) really work like
>> that ?
>> I was more thinking/guess that we have to do the math and keep the device
>> nr. per topic - wondering now, summers, what actually happens if device
>> 1.000.001 registers w/ the topic? Does GCM fail the device ?
>>
>
> As far as Google's docs say, the device will register with GCM but the
> topics will fail to send on the server.
>
> Specifically when we send the post to Google we will receive a failure
> messages TOO_MANY_DEVICES.  See the GCM Sender in the PR for exact details.
>

ok - thanks, so in case of this error - nothing is delivered? or just the
first 1M ?




>
>
>>
>>> Additionally we get an ability to configure these two message routes
>>> individually on the JMS level (better utilization, transact-ability, fail
>>> over).
>>>
>>
>> but generally, I think these are two completely different cases,
>> therefore we need to different senders
>>
>>>
>>>
>>> What do you think?
>>>
>>>
>>> Cheers,
>>>
>>> ~ Lukas
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> 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/20150812/7e787cd7/attachment-0001.html 

From supittma at redhat.com  Wed Aug 12 11:04:12 2015
From: supittma at redhat.com (Summers Pittman)
Date: Wed, 12 Aug 2015 11:04:12 -0400
Subject: [aerogear-dev] GCM Topics - split into two sender
	implementations?
In-Reply-To: <CAAg5f2RY4xXfY7UiZ_e30it4iVdYR+tiFXWsoMqB+2Zn8RTZJA@mail.gmail.com>
References: <CAEroY37VCG2VxuyjYTZrbhcoq1QJm2zMAzaDuPPeXkzcdoBVTg@mail.gmail.com>
	<CAAg5f2S77Vr3qTpABHDLBDtFhuyqpDh+qxGgrfrPfEYVDAaOCg@mail.gmail.com>
	<CAEQz2CvideoJ=APdN3uZbNqia63A-tzAYMOYmRMOd_RBAdHEJQ@mail.gmail.com>
	<CAAg5f2RY4xXfY7UiZ_e30it4iVdYR+tiFXWsoMqB+2Zn8RTZJA@mail.gmail.com>
Message-ID: <CAEQz2Cs81z9h=Hw6AjVvj06EsoWfpfoWqd1ks4p8UPVbWVorgA@mail.gmail.com>

On Wed, Aug 12, 2015 at 9:41 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Wed, Aug 12, 2015 at 3:36 PM, Summers Pittman <supittma at redhat.com>
> wrote:
>
>>
>>
>> On Wed, Aug 12, 2015 at 9:31 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>>
>>>
>>> On Wed, Aug 12, 2015 at 3:22 PM, Luk?? Fry? <lukas at fryc.eu> wrote:
>>>
>>>> Hi guys,
>>>>
>>>> /wrt the GCM Topics support PR
>>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/626
>>>>
>>>> me and summersp have discussed how JMS should be used to route messages.
>>>>
>>>>
>>>> Current implementation loads tokens and conditionally sends either
>>>> message with registration IDs or topics.
>>>>
>>>> There are two things yet to be solved:
>>>>
>>>>    -  topics can be used up to 1 million registrations, otherwise you
>>>>    have to fall back to enumerating registration IDs
>>>>    - implementation with one sender (GCMPushNotificationSender) is
>>>>    suboptimal
>>>>       - the utilization of the topics can be increased by prioritizing
>>>>       topic message sending first (covering multiple, potentially thousands
>>>>       registrations)
>>>>       - followed by sending registration IDs out
>>>>
>>>>
>>>> That's why I suggested to split implementation to two JMS queues
>>>> talking to two sender impls (e.g. GCMTopicSender
>>>> and GCMRegistrationIdsSender).
>>>>
>>>>    - first we send out topic based messages (for efficiency)
>>>>    - we collect those topics that fail and resend them for processing
>>>>    as registration IDs (fail over)
>>>>       - registration ids sending can start in parallel, but it can't
>>>>       end until we sent out all topics
>>>>
>>>>
>>> I agree that we need a slip here - but does it (GCM) really work like
>>> that ?
>>> I was more thinking/guess that we have to do the math and keep the
>>> device nr. per topic - wondering now, summers, what actually happens if
>>> device 1.000.001 registers w/ the topic? Does GCM fail the device ?
>>>
>>
>> As far as Google's docs say, the device will register with GCM but the
>> topics will fail to send on the server.
>>
>> Specifically when we send the post to Google we will receive a failure
>> messages TOO_MANY_DEVICES.  See the GCM Sender in the PR for exact details.
>>
>
> ok - thanks, so in case of this error - nothing is delivered? or just the
> first 1M ?
>
That is undocumented, but I would assume nothing is delivered.

>
>
>
>
>>
>>
>>>
>>>> Additionally we get an ability to configure these two message routes
>>>> individually on the JMS level (better utilization, transact-ability, fail
>>>> over).
>>>>
>>>
>>> but generally, I think these are two completely different cases,
>>> therefore we need to different senders
>>>
>>>>
>>>>
>>>> What do you think?
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> ~ Lukas
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> 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/20150812/41b3739f/attachment.html 

From daniel.bevenius at gmail.com  Thu Aug 13 02:36:18 2015
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Thu, 13 Aug 2015 08:36:18 +0200
Subject: [aerogear-dev] UPS Migrator error (1.1.0.Final)
In-Reply-To: <CALimhXp7kzjL3vCFfYs8Fc8NmdNn2h2BdQbO8mR-byrXQhi90A@mail.gmail.com>
References: <CALimhXp7kzjL3vCFfYs8Fc8NmdNn2h2BdQbO8mR-byrXQhi90A@mail.gmail.com>
Message-ID: <CAFJm-3H5Oomgr91Tvk0vjEmYCdPtocbE-3Huy2ALF40V2FF9hg@mail.gmail.com>

Hi,

can you tell me what version of MySql you are using and also the steps to
reproduce?

Thanks,

/Dan

On 12 August 2015 at 12:37, Oleg Matskiv <omatskiv at redhat.com> wrote:

> Hi,
> can somebody who worked on UPS migrator recently, check if it deals with
> recent database changes (e.g.
> https://github.com/aerogear/aerogear-unifiedpush-server/commit/bbe1c0e80a4a5295a3c7cefe66f5e8cc07da66be#diff-23e531d12489411024ea5c379be1d178R70
> ).
>
> I have run into error when running integration test with migrator run
> (liquibase.exception.DatabaseException:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Key column
> 'variantInformations_id' doesn't exist in table).
>
> Thanks for any help.
>
> --
> Oleg Matskiv
> Mobile QE Intern
> omatskiv at redhat.com
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150813/53f6e2c8/attachment.html 

From matzew at apache.org  Thu Aug 13 02:36:31 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 13 Aug 2015 08:36:31 +0200
Subject: [aerogear-dev] UPS Migrator error (1.1.0.Final)
In-Reply-To: <CALimhXp7kzjL3vCFfYs8Fc8NmdNn2h2BdQbO8mR-byrXQhi90A@mail.gmail.com>
References: <CALimhXp7kzjL3vCFfYs8Fc8NmdNn2h2BdQbO8mR-byrXQhi90A@mail.gmail.com>
Message-ID: <CAAg5f2RaezsxfsfzwdCuBVOQi6ek61UrJwJkLPyZr9trVkQzZQ@mail.gmail.com>

Oleg,

did you create a JIRA?

On Wed, Aug 12, 2015 at 12:37 PM, Oleg Matskiv <omatskiv at redhat.com> wrote:

> Hi,
> can somebody who worked on UPS migrator recently, check if it deals with
> recent database changes (e.g.
> https://github.com/aerogear/aerogear-unifiedpush-server/commit/bbe1c0e80a4a5295a3c7cefe66f5e8cc07da66be#diff-23e531d12489411024ea5c379be1d178R70
> ).
>
> I have run into error when running integration test with migrator run
> (liquibase.exception.DatabaseException:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Key column
> 'variantInformations_id' doesn't exist in table).
>
> Thanks for any help.
>
> --
> Oleg Matskiv
> Mobile QE Intern
> omatskiv at redhat.com
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From daniel.bevenius at gmail.com  Thu Aug 13 03:17:16 2015
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Thu, 13 Aug 2015 09:17:16 +0200
Subject: [aerogear-dev] UPS Migrator error (1.1.0.Final)
In-Reply-To: <CALimhXp7kzjL3vCFfYs8Fc8NmdNn2h2BdQbO8mR-byrXQhi90A@mail.gmail.com>
References: <CALimhXp7kzjL3vCFfYs8Fc8NmdNn2h2BdQbO8mR-byrXQhi90A@mail.gmail.com>
Message-ID: <CAFJm-3HQNTrPAFOjc0NaGGC0yfbuGkZ4xdcPdCrb-EGXbmzd_Q@mail.gmail.com>

Hi Oleg,

I was able to reproduce this using the following steps:
https://gist.github.com/danbev/d27e5260c480d8a0c743#file-qu-reported-md

I'm looking into this now.

Thanks,

/Dan

On 12 August 2015 at 12:37, Oleg Matskiv <omatskiv at redhat.com> wrote:

> Hi,
> can somebody who worked on UPS migrator recently, check if it deals with
> recent database changes (e.g.
> https://github.com/aerogear/aerogear-unifiedpush-server/commit/bbe1c0e80a4a5295a3c7cefe66f5e8cc07da66be#diff-23e531d12489411024ea5c379be1d178R70
> ).
>
> I have run into error when running integration test with migrator run
> (liquibase.exception.DatabaseException:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Key column
> 'variantInformations_id' doesn't exist in table).
>
> Thanks for any help.
>
> --
> Oleg Matskiv
> Mobile QE Intern
> omatskiv at redhat.com
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150813/5b8726bd/attachment-0001.html 

From omatskiv at redhat.com  Thu Aug 13 03:45:31 2015
From: omatskiv at redhat.com (Oleg Matskiv)
Date: Thu, 13 Aug 2015 09:45:31 +0200
Subject: [aerogear-dev] UPS Migrator error (1.1.0.Final)
In-Reply-To: <CALimhXp7kzjL3vCFfYs8Fc8NmdNn2h2BdQbO8mR-byrXQhi90A@mail.gmail.com>
References: <CALimhXp7kzjL3vCFfYs8Fc8NmdNn2h2BdQbO8mR-byrXQhi90A@mail.gmail.com>
Message-ID: <CALimhXqW1z2FyZx6_kodOdhGgYgS6E7b-PRk-YKs06ch5fLJiQ@mail.gmail.com>

Dan:
I have read that you have already reproduce, but anyway: version:
5.5.45 MySQL Community Server. I just created empty DB and ran
integration test with wildfly8UpsFromMavenRepository provider.
First it couldn't find "adm_variant" table (because of this i think:
https://github.com/aerogear/aerogear-unifiedpush-server/commit/7d61152b1eddaf11e5a732d8b7499828e15a2756).
So I tried to with runMigrator option and got that error about column
'variantInformations_id'..

Matthias:

I did not create JIRA because this is for me first time working with
UPS and I thought that the mistake could simply be just on my side...


On Wed, Aug 12, 2015 at 12:37 PM, Oleg Matskiv <omatskiv at redhat.com> wrote:

> Hi,
> can somebody who worked on UPS migrator recently, check if it deals with
> recent database changes (e.g.
> https://github.com/aerogear/aerogear-unifiedpush-server/commit/bbe1c0e80a4a5295a3c7cefe66f5e8cc07da66be#diff-23e531d12489411024ea5c379be1d178R70
> ).
>
> I have run into error when running integration test with migrator run
> (liquibase.exception.DatabaseException:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Key column
> 'variantInformations_id' doesn't exist in table).
>
> Thanks for any help.
>
> --
> Oleg Matskiv
> Mobile QE Intern
> omatskiv at redhat.com
>



-- 
Oleg Matskiv
Mobile QE Intern
omatskiv at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150813/cd088760/attachment.html 

From scm.blanc at gmail.com  Thu Aug 13 03:47:51 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 13 Aug 2015 09:47:51 +0200
Subject: [aerogear-dev] UPS Migrator error (1.1.0.Final)
In-Reply-To: <CALimhXqW1z2FyZx6_kodOdhGgYgS6E7b-PRk-YKs06ch5fLJiQ@mail.gmail.com>
References: <CALimhXp7kzjL3vCFfYs8Fc8NmdNn2h2BdQbO8mR-byrXQhi90A@mail.gmail.com>
	<CALimhXqW1z2FyZx6_kodOdhGgYgS6E7b-PRk-YKs06ch5fLJiQ@mail.gmail.com>
Message-ID: <CAD_dpu2_AsvLi7+__SECZhXzEyrGsK6+qDoJwA6nM_OfgsN9Nw@mail.gmail.com>

On Thu, Aug 13, 2015 at 9:45 AM, Oleg Matskiv <omatskiv at redhat.com> wrote:

> Dan:
> I have read that you have already reproduce, but anyway: version: 5.5.45 MySQL Community Server. I just created empty DB and ran integration test with wildfly8UpsFromMavenRepository provider.
> First it couldn't find "adm_variant" table (because of this i think: https://github.com/aerogear/aerogear-unifiedpush-server/commit/7d61152b1eddaf11e5a732d8b7499828e15a2756). So I tried to with runMigrator option and got that error about column 'variantInformations_id'..
>
> Matthias:
>
> I did not create JIRA because this is for me first time working with UPS and I thought that the mistake could simply be just on my side...
>
> Jira tickets are cheap :) please create one :)

>
> On Wed, Aug 12, 2015 at 12:37 PM, Oleg Matskiv <omatskiv at redhat.com>
> wrote:
>
>> Hi,
>> can somebody who worked on UPS migrator recently, check if it deals with
>> recent database changes (e.g.
>> https://github.com/aerogear/aerogear-unifiedpush-server/commit/bbe1c0e80a4a5295a3c7cefe66f5e8cc07da66be#diff-23e531d12489411024ea5c379be1d178R70
>> ).
>>
>> I have run into error when running integration test with migrator run
>> (liquibase.exception.DatabaseException:
>> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Key column
>> 'variantInformations_id' doesn't exist in table).
>>
>> Thanks for any help.
>>
>> --
>> Oleg Matskiv
>> Mobile QE Intern
>> omatskiv at redhat.com
>>
>
>
>
> --
> Oleg Matskiv
> Mobile QE Intern
> omatskiv at redhat.com
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150813/995a05fa/attachment.html 

From omatskiv at redhat.com  Thu Aug 13 04:03:41 2015
From: omatskiv at redhat.com (Oleg Matskiv)
Date: Thu, 13 Aug 2015 10:03:41 +0200
Subject: [aerogear-dev] UPS Migrator error (1.1.0.Final)
In-Reply-To: <CAD_dpu2_AsvLi7+__SECZhXzEyrGsK6+qDoJwA6nM_OfgsN9Nw@mail.gmail.com>
References: <CALimhXp7kzjL3vCFfYs8Fc8NmdNn2h2BdQbO8mR-byrXQhi90A@mail.gmail.com>
	<CALimhXqW1z2FyZx6_kodOdhGgYgS6E7b-PRk-YKs06ch5fLJiQ@mail.gmail.com>
	<CAD_dpu2_AsvLi7+__SECZhXzEyrGsK6+qDoJwA6nM_OfgsN9Nw@mail.gmail.com>
Message-ID: <CALimhXo2CvXZu-wH7ZXuJnuwo3A4TBopKzoiPnvjY_xah14n3Q@mail.gmail.com>

OK, created.
https://issues.jboss.org/browse/AEROGEAR-1690

On Thu, Aug 13, 2015 at 9:47 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

>
>
> On Thu, Aug 13, 2015 at 9:45 AM, Oleg Matskiv <omatskiv at redhat.com> wrote:
>
>> Dan:
>> I have read that you have already reproduce, but anyway: version: 5.5.45 MySQL Community Server. I just created empty DB and ran integration test with wildfly8UpsFromMavenRepository provider.
>> First it couldn't find "adm_variant" table (because of this i think: https://github.com/aerogear/aerogear-unifiedpush-server/commit/7d61152b1eddaf11e5a732d8b7499828e15a2756). So I tried to with runMigrator option and got that error about column 'variantInformations_id'..
>>
>> Matthias:
>>
>> I did not create JIRA because this is for me first time working with UPS and I thought that the mistake could simply be just on my side...
>>
>> Jira tickets are cheap :) please create one :)
>
>>
>> On Wed, Aug 12, 2015 at 12:37 PM, Oleg Matskiv <omatskiv at redhat.com>
>> wrote:
>>
>>> Hi,
>>> can somebody who worked on UPS migrator recently, check if it deals with
>>> recent database changes (e.g.
>>> https://github.com/aerogear/aerogear-unifiedpush-server/commit/bbe1c0e80a4a5295a3c7cefe66f5e8cc07da66be#diff-23e531d12489411024ea5c379be1d178R70
>>> ).
>>>
>>> I have run into error when running integration test with migrator run
>>> (liquibase.exception.DatabaseException:
>>> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Key column
>>> 'variantInformations_id' doesn't exist in table).
>>>
>>> Thanks for any help.
>>>
>>> --
>>> Oleg Matskiv
>>> Mobile QE Intern
>>> omatskiv at redhat.com
>>>
>>
>>
>>
>> --
>> Oleg Matskiv
>> Mobile QE Intern
>> omatskiv at redhat.com
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Oleg Matskiv
Mobile QE Intern
omatskiv at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150813/ea4a10f1/attachment.html 

From daniel.bevenius at gmail.com  Thu Aug 13 05:08:18 2015
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Thu, 13 Aug 2015 11:08:18 +0200
Subject: [aerogear-dev] UPS Migrator error (1.1.0.Final)
In-Reply-To: <CALimhXo2CvXZu-wH7ZXuJnuwo3A4TBopKzoiPnvjY_xah14n3Q@mail.gmail.com>
References: <CALimhXp7kzjL3vCFfYs8Fc8NmdNn2h2BdQbO8mR-byrXQhi90A@mail.gmail.com>
	<CALimhXqW1z2FyZx6_kodOdhGgYgS6E7b-PRk-YKs06ch5fLJiQ@mail.gmail.com>
	<CAD_dpu2_AsvLi7+__SECZhXzEyrGsK6+qDoJwA6nM_OfgsN9Nw@mail.gmail.com>
	<CALimhXo2CvXZu-wH7ZXuJnuwo3A4TBopKzoiPnvjY_xah14n3Q@mail.gmail.com>
Message-ID: <CAFJm-3GtQreHGsk3sf9w6xMkpPON_NOGwUR0sj_JnM9Gf4_8CA@mail.gmail.com>

Thanks for the info Oleg. I've added a comment to the JIRA. Could you guys
take a look and see if this makes sense to you?

Thanks,

/Dan

On 13 August 2015 at 10:03, Oleg Matskiv <omatskiv at redhat.com> wrote:

> OK, created.
> https://issues.jboss.org/browse/AEROGEAR-1690
>
> On Thu, Aug 13, 2015 at 9:47 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>>
>>
>> On Thu, Aug 13, 2015 at 9:45 AM, Oleg Matskiv <omatskiv at redhat.com>
>> wrote:
>>
>>> Dan:
>>> I have read that you have already reproduce, but anyway: version: 5.5.45 MySQL Community Server. I just created empty DB and ran integration test with wildfly8UpsFromMavenRepository provider.
>>> First it couldn't find "adm_variant" table (because of this i think: https://github.com/aerogear/aerogear-unifiedpush-server/commit/7d61152b1eddaf11e5a732d8b7499828e15a2756). So I tried to with runMigrator option and got that error about column 'variantInformations_id'..
>>>
>>> Matthias:
>>>
>>> I did not create JIRA because this is for me first time working with UPS and I thought that the mistake could simply be just on my side...
>>>
>>> Jira tickets are cheap :) please create one :)
>>
>>>
>>> On Wed, Aug 12, 2015 at 12:37 PM, Oleg Matskiv <omatskiv at redhat.com>
>>> wrote:
>>>
>>>> Hi,
>>>> can somebody who worked on UPS migrator recently, check if it deals
>>>> with recent database changes (e.g.
>>>> https://github.com/aerogear/aerogear-unifiedpush-server/commit/bbe1c0e80a4a5295a3c7cefe66f5e8cc07da66be#diff-23e531d12489411024ea5c379be1d178R70
>>>> ).
>>>>
>>>> I have run into error when running integration test with migrator run
>>>> (liquibase.exception.DatabaseException:
>>>> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Key column
>>>> 'variantInformations_id' doesn't exist in table).
>>>>
>>>> Thanks for any help.
>>>>
>>>> --
>>>> Oleg Matskiv
>>>> Mobile QE Intern
>>>> omatskiv at redhat.com
>>>>
>>>
>>>
>>>
>>> --
>>> Oleg Matskiv
>>> Mobile QE Intern
>>> omatskiv at redhat.com
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Oleg Matskiv
> Mobile QE Intern
> omatskiv at redhat.com
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150813/1a1362ae/attachment-0001.html 

From lukas.fryc at gmail.com  Thu Aug 13 07:42:53 2015
From: lukas.fryc at gmail.com (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Thu, 13 Aug 2015 13:42:53 +0200
Subject: [aerogear-dev] GCM Topics - split into two sender
	implementations?
In-Reply-To: <CAAg5f2S77Vr3qTpABHDLBDtFhuyqpDh+qxGgrfrPfEYVDAaOCg@mail.gmail.com>
References: <CAEroY37VCG2VxuyjYTZrbhcoq1QJm2zMAzaDuPPeXkzcdoBVTg@mail.gmail.com>
	<CAAg5f2S77Vr3qTpABHDLBDtFhuyqpDh+qxGgrfrPfEYVDAaOCg@mail.gmail.com>
Message-ID: <CAEroY37LmtBbXR3bS2+Y13fLvSs1syNnvUbay79Tq30oHusK3w@mail.gmail.com>

On Wed, Aug 12, 2015 at 3:31 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Wed, Aug 12, 2015 at 3:22 PM, Luk?? Fry? <lukas at fryc.eu> wrote:
>
>> Hi guys,
>>
>> /wrt the GCM Topics support PR
>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/626
>>
>> me and summersp have discussed how JMS should be used to route messages.
>>
>>
>> Current implementation loads tokens and conditionally sends either
>> message with registration IDs or topics.
>>
>> There are two things yet to be solved:
>>
>>    -  topics can be used up to 1 million registrations, otherwise you
>>    have to fall back to enumerating registration IDs
>>    - implementation with one sender (GCMPushNotificationSender) is
>>    suboptimal
>>       - the utilization of the topics can be increased by prioritizing
>>       topic message sending first (covering multiple, potentially thousands
>>       registrations)
>>       - followed by sending registration IDs out
>>
>>
>> That's why I suggested to split implementation to two JMS queues talking
>> to two sender impls (e.g. GCMTopicSender and GCMRegistrationIdsSender).
>>
>>    - first we send out topic based messages (for efficiency)
>>    - we collect those topics that fail and resend them for processing as
>>    registration IDs (fail over)
>>       - registration ids sending can start in parallel, but it can't end
>>       until we sent out all topics
>>
>>
> I agree that we need a slip here - but does it (GCM) really work like that
> ?
> I was more thinking/guess that we have to do the math and keep the device
> nr. per topic
>

Yes, that's certainly possible in a case we are able to find registration
IDs for all devices subscribed to a given topic.

Actually our current strategy for detecting end of sending session is based
on token (device) counting.



> - wondering now, summers, what actually happens if device 1.000.001
> registers w/ the topic? Does GCM fail the device ?
>
>
>> Additionally we get an ability to configure these two message routes
>> individually on the JMS level (better utilization, transact-ability, fail
>> over).
>>
>
> but generally, I think these are two completely different cases, therefore
> we need to different senders
>
>>
>>
>> What do you think?
>>
>>
>> Cheers,
>>
>> ~ Lukas
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> 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/20150813/ffed16f8/attachment.html 

From edewit at redhat.com  Thu Aug 13 12:41:20 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Thu, 13 Aug 2015 18:41:20 +0200
Subject: [aerogear-dev] ng-cordova
Message-ID: <CAO2B-faWyK9QJmuEGeO6FGaD9-G8dOxEc7sPkb52hVEYgHxGag@mail.gmail.com>

Hi,

You might remember that we wanted to add the aerogear push plugin to the
ng-cordova project. So we create the PR, half a year ago and now 3 PR's [1]
later we have been added! Now getting started with cordova, angular and
push is super easy. Keep an eye out for the next release.

[1] https://github.com/driftyco/ng-cordova/pull/933
-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150813/4cd0d42e/attachment.html 

From scm.blanc at gmail.com  Thu Aug 13 12:43:47 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 13 Aug 2015 18:43:47 +0200
Subject: [aerogear-dev] [Aerogear-users] ng-cordova
In-Reply-To: <CAO2B-faWyK9QJmuEGeO6FGaD9-G8dOxEc7sPkb52hVEYgHxGag@mail.gmail.com>
References: <CAO2B-faWyK9QJmuEGeO6FGaD9-G8dOxEc7sPkb52hVEYgHxGag@mail.gmail.com>
Message-ID: <CAD_dpu1zGUgqtST5awwxGdxvguBp9cNJmP+bCfobMNBJnFXaHw@mail.gmail.com>

\o/
This is really cool

On Thu, Aug 13, 2015 at 6:41 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi,
>
> You might remember that we wanted to add the aerogear push plugin to the
> ng-cordova project. So we create the PR, half a year ago and now 3 PR's [1]
> later we have been added! Now getting started with cordova, angular and
> push is super easy. Keep an eye out for the next release.
>
> [1] https://github.com/driftyco/ng-cordova/pull/933
> --
> Cheers,
>        Erik Jan
>
> _______________________________________________
> 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/20150813/46dca26b/attachment.html 

From idel.pivnitskiy at gmail.com  Fri Aug 14 22:09:54 2015
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Sat, 15 Aug 2015 05:09:54 +0300
Subject: [aerogear-dev] WebPush Server supports the latest
	draft-ietf-webpush-protocol-00
Message-ID: <CAN+BUJo_KOjgdeQh3Yz98raGSnXrbiMrZSc4tZ_n=9x2YA+AQw@mail.gmail.com>

Hi all!

I'm happy to announce, that you are able to play with the latest draft of
WebPush protocol. Our WebPush Server and Console are updated now. The new
draft has too many changes, try it :)

For more information, see
https://github.com/aerogear/aerogear-webpush-server/pull/14

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

From kpiwko at redhat.com  Mon Aug 17 03:08:42 2015
From: kpiwko at redhat.com (Karel Piwko)
Date: Mon, 17 Aug 2015 09:08:42 +0200
Subject: [aerogear-dev] Breaking changes in between UPS 1.1.0.Beta3 and
	1.1.0.Final
Message-ID: <CAPXQee4NaekqsSO14zjrStBNXbBqXusT431d7tKAhAuX1MREVA@mail.gmail.com>

Hello All,

I'm really unhappy with number of breaking changes that has appeared in the
latest staged 1.1.0.Final - mostly these changes were related to massive DB
schema updates. I'd expect such changes to happen in Alpha phase and not in
between Beta3 and Final.

I understand that a lot of these changes have been driven by late inclusion
of migrator to 1.1 branch. That said, what is the plan with 1.1.0.Final?
Are you guys going to remove the changes or at least make sure they do not
impact users running Beta3? I've seen it has been de-staged and there have
been a few commits reverting DB changes back. Is there any estimate when
1.1.0.Final will be restaged?

QE plan is to make sure that migration from 1.0.3 is smooth, however we
also want migration from Beta3 to be smooth.

Many thanks,

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

From matzew at apache.org  Mon Aug 17 05:53:07 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 17 Aug 2015 11:53:07 +0200
Subject: [aerogear-dev] Breaking changes in between UPS 1.1.0.Beta3 and
	1.1.0.Final
In-Reply-To: <CAPXQee4NaekqsSO14zjrStBNXbBqXusT431d7tKAhAuX1MREVA@mail.gmail.com>
References: <CAPXQee4NaekqsSO14zjrStBNXbBqXusT431d7tKAhAuX1MREVA@mail.gmail.com>
Message-ID: <CAAg5f2Qta-vPw6zywnUqeaWC66UOi8K9+76XD-K6_ez2kLg+FQ@mail.gmail.com>

Hi Karel,

On Mon, Aug 17, 2015 at 9:08 AM, Karel Piwko <kpiwko at redhat.com> wrote:

> Hello All,
>
> I'm really unhappy with number of breaking changes that has appeared in
> the latest staged 1.1.0.Final - mostly these changes were related to
> massive DB schema updates. I'd expect such changes to happen in Alpha phase
> and not in between Beta3 and Final.
>

I fully understand your frustration. I think the source of this issue is
that the migration work took much longer than expected, getting it ported
to master branch (was introduced on 1.0.3).


>
> I understand that a lot of these changes have been driven by late
> inclusion of migrator to 1.1 branch. That said, what is the plan with
> 1.1.0.Final? Are you guys going to remove the changes or at least make sure
> they do not impact users running Beta3?
>

I think the biggest concern is clearly supporting users, upgrading from
1.0.3


> I've seen it has been de-staged and there have been a few commits
> reverting DB changes back. Is there any estimate when 1.1.0.Final will be
> restaged?
>

Yeah, there will be a re-staging coming soon. Question, due to the huge
changes, what about doing a Beta.4 and following up w a .Final in week or
two?
To make sure things are stable, before we stage a 1.1.0.Final - makes sense
?


>
> QE plan is to make sure that migration from 1.0.3 is smooth, however we
> also want migration from Beta3 to be smooth.
>

I am actually over asked about the migration from beta.3, not sure that's
really a huge concern here


>
> Many thanks,
>
> Karel
>
> _______________________________________________
> 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/20150817/ff49e07d/attachment-0001.html 

From kpiwko at redhat.com  Mon Aug 17 10:52:01 2015
From: kpiwko at redhat.com (Karel Piwko)
Date: Mon, 17 Aug 2015 16:52:01 +0200
Subject: [aerogear-dev] Breaking changes in between UPS 1.1.0.Beta3 and
	1.1.0.Final
In-Reply-To: <CAAg5f2Qta-vPw6zywnUqeaWC66UOi8K9+76XD-K6_ez2kLg+FQ@mail.gmail.com>
References: <CAPXQee4NaekqsSO14zjrStBNXbBqXusT431d7tKAhAuX1MREVA@mail.gmail.com>
	<CAAg5f2Qta-vPw6zywnUqeaWC66UOi8K9+76XD-K6_ez2kLg+FQ@mail.gmail.com>
Message-ID: <CAPXQee4mWYkOpbTmP3WsBXTL2DKebhXmL9wvqNpzrrieRuERqg@mail.gmail.com>

Thanks Matthias,

Comments inline.

Karel

Dne 17. 8. 2015 11:54 napsal u?ivatel "Matthias Wessendorf" <
matzew at apache.org>:
>
> Hi Karel,
>
> On Mon, Aug 17, 2015 at 9:08 AM, Karel Piwko <kpiwko at redhat.com> wrote:
>>
>> Hello All,
>>
>> I'm really unhappy with number of breaking changes that has appeared in
the latest staged 1.1.0.Final - mostly these changes were related to
massive DB schema updates. I'd expect such changes to happen in Alpha phase
and not in between Beta3 and Final.
>
>
> I fully understand your frustration. I think the source of this issue is
that the migration work took much longer than expected, getting it ported
to master branch (was introduced on 1.0.3).
>
>>
>>
>> I understand that a lot of these changes have been driven by late
inclusion of migrator to 1.1 branch. That said, what is the plan with
1.1.0.Final? Are you guys going to remove the changes or at least make sure
they do not impact users running Beta3?
>
>
> I think the biggest concern is clearly supporting users, upgrading from
1.0.3
>
>>
>> I've seen it has been de-staged and there have been a few commits
reverting DB changes back. Is there any estimate when 1.1.0.Final will be
restaged?
>
>
> Yeah, there will be a re-staging coming soon. Question, due to the huge
changes, what about doing a Beta.4 and following up w a .Final in week or
two?
> To make sure things are stable, before we stage a 1.1.0.Final - makes
sense ?

Sounds good to me!

>
>>
>>
>> QE plan is to make sure that migration from 1.0.3 is smooth, however we
also want migration from Beta3 to be smooth.
>
>
> I am actually over asked about the migration from beta.3, not sure that's
really a huge concern here

If that's not required, we can obviously skip such testing.
>
>>
>>
>> Many thanks,
>>
>> Karel
>>
>> _______________________________________________
>> 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/20150817/03f0561a/attachment.html 

From matzew at apache.org  Mon Aug 17 11:09:33 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 17 Aug 2015 17:09:33 +0200
Subject: [aerogear-dev] Breaking changes in between UPS 1.1.0.Beta3 and
	1.1.0.Final
In-Reply-To: <CAPXQee4mWYkOpbTmP3WsBXTL2DKebhXmL9wvqNpzrrieRuERqg@mail.gmail.com>
References: <CAPXQee4NaekqsSO14zjrStBNXbBqXusT431d7tKAhAuX1MREVA@mail.gmail.com>
	<CAAg5f2Qta-vPw6zywnUqeaWC66UOi8K9+76XD-K6_ez2kLg+FQ@mail.gmail.com>
	<CAPXQee4mWYkOpbTmP3WsBXTL2DKebhXmL9wvqNpzrrieRuERqg@mail.gmail.com>
Message-ID: <CAAg5f2SMbS1-zS0nExj+svtL58iAfh2EWTqqqww5FnOw=jSyAA@mail.gmail.com>

On Mon, Aug 17, 2015 at 4:52 PM, Karel Piwko <kpiwko at redhat.com> wrote:

> Thanks Matthias,
>
> Comments inline.
>
> Karel
>
> Dne 17. 8. 2015 11:54 napsal u?ivatel "Matthias Wessendorf" <
> matzew at apache.org>:
> >
> > Hi Karel,
> >
> > On Mon, Aug 17, 2015 at 9:08 AM, Karel Piwko <kpiwko at redhat.com> wrote:
> >>
> >> Hello All,
> >>
> >> I'm really unhappy with number of breaking changes that has appeared in
> the latest staged 1.1.0.Final - mostly these changes were related to
> massive DB schema updates. I'd expect such changes to happen in Alpha phase
> and not in between Beta3 and Final.
> >
> >
> > I fully understand your frustration. I think the source of this issue is
> that the migration work took much longer than expected, getting it ported
> to master branch (was introduced on 1.0.3).
> >
> >>
> >>
> >> I understand that a lot of these changes have been driven by late
> inclusion of migrator to 1.1 branch. That said, what is the plan with
> 1.1.0.Final? Are you guys going to remove the changes or at least make sure
> they do not impact users running Beta3?
> >
> >
> > I think the biggest concern is clearly supporting users, upgrading from
> 1.0.3
> >
> >>
> >> I've seen it has been de-staged and there have been a few commits
> reverting DB changes back. Is there any estimate when 1.1.0.Final will be
> restaged?
> >
> >
> > Yeah, there will be a re-staging coming soon. Question, due to the huge
> changes, what about doing a Beta.4 and following up w a .Final in week or
> two?
> > To make sure things are stable, before we stage a 1.1.0.Final - makes
> sense ?
>
> Sounds good to me!
>
> >
> >>
> >>
> >> QE plan is to make sure that migration from 1.0.3 is smooth, however we
> also want migration from Beta3 to be smooth.
> >
> >
> > I am actually over asked about the migration from beta.3, not sure
> that's really a huge concern here
>
> If that's not required, we can obviously skip such testing.
>

yeah, sounds good to me!

Ok, Karel, again, I understand the pain, and I will do a beta.4 staging
later this evening!


>
> >
> >>
> >>
> >> Many thanks,
> >>
> >> Karel
> >>
> >> _______________________________________________
> >> 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/20150817/4d4fc9d2/attachment.html 

From matzew at apache.org  Mon Aug 17 14:28:00 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 17 Aug 2015 20:28:00 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.0-beta.4 (was: Re: Staging of UPS
	1.1.0.Final)
Message-ID: <CAAg5f2RUGDkquu+xV00PMVTr57s2QoMa_tYJ86YhThJ6c5bs1A@mail.gmail.com>

Hello,

since we had a few issues found and serious changes on the underlying DB
schema (see Karel's mail), here is the staging of another beta:

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



Idea is to afterwards have a stable time of a week, and get the
1.1.0.Final, finally out!

Any comments?

-Matthias


On Wed, Aug 12, 2015 at 8:52 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Yes, I will discard the current staged release.
> Thanks Erik for reporting these issues.
>
>
>
> On Tue, Aug 11, 2015 at 10:39 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> I think this is aldo worth to be included to 1.1.0.Final
>>
>>
>> On Tuesday, August 11, 2015, Erik Jan de Wit <edewit at redhat.com> wrote:
>>
>>> I found these issues:
>>>
>>>
>>>    1. AGPUSH-1492 <https://issues.jboss.org/browse/AGPUSH-1492> Deleting
>>>    an Application leaves installations
>>>    2.
>>>       1.
>>>          1. AGPUSH-1491 <https://issues.jboss.org/browse/AGPUSH-1491> Android
>>>          doesn't show installations
>>>
>>>
>>> On Tue, Aug 11, 2015 at 1:06 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> looking...
>>>>
>>>> On Fri, Aug 7, 2015 at 3:48 PM, Sebastien Blanc <scm.blanc at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi team,
>>>>>
>>>>> I'm happy to announce that UPS 1.1.0 Final has been staged.
>>>>>
>>>>> Please test the staged release :
>>>>>
>>>>>
>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6277
>>>>>
>>>>> On Wednesday I'd like to press the button to release it to the wild.
>>>>>
>>>>> Sebi
>>>>>
>>>>> ps : the openshift update will follow
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>
>>
>>
>> --
>> Sent from Gmail Mobile
>>
>> _______________________________________________
>> 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/20150817/010a30f0/attachment-0001.html 

From matzew at apache.org  Mon Aug 17 15:09:40 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 17 Aug 2015 21:09:40 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.0-beta.4 (was: Re: Staging of
 UPS 1.1.0.Final)
In-Reply-To: <CAAg5f2RUGDkquu+xV00PMVTr57s2QoMa_tYJ86YhThJ6c5bs1A@mail.gmail.com>
References: <CAAg5f2RUGDkquu+xV00PMVTr57s2QoMa_tYJ86YhThJ6c5bs1A@mail.gmail.com>
Message-ID: <CAAg5f2Sh5CqDLQ-A4+kLmA7rbyUKNy8-YqQOMNJC7GSzJe2pcg@mail.gmail.com>

and here comes the Openshift PR:

https://github.com/aerogear/openshift-origin-cartridge-aerogear-push/pull/21

On Mon, Aug 17, 2015 at 8:28 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hello,
>
> since we had a few issues found and serious changes on the underlying DB
> schema (see Karel's mail), here is the staging of another beta:
>
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6332/
>
>
>
> Idea is to afterwards have a stable time of a week, and get the
> 1.1.0.Final, finally out!
>
> Any comments?
>
> -Matthias
>
>
> On Wed, Aug 12, 2015 at 8:52 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> Yes, I will discard the current staged release.
>> Thanks Erik for reporting these issues.
>>
>>
>>
>> On Tue, Aug 11, 2015 at 10:39 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> I think this is aldo worth to be included to 1.1.0.Final
>>>
>>>
>>> On Tuesday, August 11, 2015, Erik Jan de Wit <edewit at redhat.com> wrote:
>>>
>>>> I found these issues:
>>>>
>>>>
>>>>    1. AGPUSH-1492 <https://issues.jboss.org/browse/AGPUSH-1492> Deleting
>>>>    an Application leaves installations
>>>>    2.
>>>>       1.
>>>>          1. AGPUSH-1491 <https://issues.jboss.org/browse/AGPUSH-1491> Android
>>>>          doesn't show installations
>>>>
>>>>
>>>> On Tue, Aug 11, 2015 at 1:06 PM, Matthias Wessendorf <matzew at apache.org
>>>> > wrote:
>>>>
>>>>> looking...
>>>>>
>>>>> On Fri, Aug 7, 2015 at 3:48 PM, Sebastien Blanc <scm.blanc at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi team,
>>>>>>
>>>>>> I'm happy to announce that UPS 1.1.0 Final has been staged.
>>>>>>
>>>>>> Please test the staged release :
>>>>>>
>>>>>>
>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6277
>>>>>>
>>>>>> On Wednesday I'd like to press the button to release it to the wild.
>>>>>>
>>>>>> Sebi
>>>>>>
>>>>>> ps : the openshift update will follow
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>
>>>
>>>
>>> --
>>> Sent from Gmail Mobile
>>>
>>> _______________________________________________
>>> 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
>



-- 
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/20150817/c05a4f4b/attachment.html 

From idel.pivnitskiy at gmail.com  Wed Aug 19 00:30:19 2015
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Wed, 19 Aug 2015 07:30:19 +0300
Subject: [aerogear-dev] AeroGear WebPush Java Client
Message-ID: <CAN+BUJo2V08gp0E7Kn-dCLABpHbe4+-ghY8wF2v5XxSD8_PLPQ@mail.gmail.com>

Hi all!

I've just implemented a lightweight java client for receiving push messages
from AeroGear WebPush Server [1]. It is easy to use and fully async!

A few words about decision to use Jetty as a HTTP/2 client:

Currently there are only 3 Java libraries, which implement client side of
HTTP/2 protocol [2]: Netty, Jetty and OkHttp. I tried all of them:

   - First of all I tried to use OkHttp. This is a lightweight http client
   for Android and other Java apps. But currently this library supports HTTP/2
   protocol only via old HTTP/1.1 API. It works well for simple
   request-response, but its client API does not allow to use HTTP/2 features,
   like Server Push Frames. I looked at GRPC [3], because Googlers use OkHttp
   for HTTP/2 transport. But they don't use public API, they use only inner
   classes to handle frames and built their own logic atop this classes. It
   would be too complicated for our purposes.
   - Secondary, I tried to refactor our WebPush console to a client
   library. But this way is complicated too. netty-codec-http2 does not
   provide a client API, it is only codec, low level protocol implementation.
   - Now I use jetty-http2-client. It is easy to configure and use, fast
   and async. Jetty provides a user friendly API to handle HTTP/2 streams and
   get PUSH_PROMISE frames.

For more information, look at my commit history.
In the future, if there will be more lightweight alternatives than Jetty
(for example, new version of OkHttp or Java 9 API), I will rewrite the
transport layer of my library.

Here is an example, how to use my library [4].

[1] https://github.com/idelpivnitskiy/aerogear-webpush-java-client
[2] https://github.com/http2/http2-spec/wiki/Implementations
[3] https://github.com/grpc/grpc-java/tree/master/okhttp
[4]
https://github.com/idelpivnitskiy/aerogear-webpush-java-client/blob/master/src/example/java/org/jboss/aerogear/webpush/Example.java

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

From kpiwko at redhat.com  Wed Aug 19 03:10:13 2015
From: kpiwko at redhat.com (Karel Piwko)
Date: Wed, 19 Aug 2015 09:10:13 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.0-beta.4 (was: Re: Staging of
 UPS 1.1.0.Final)
In-Reply-To: <CAAg5f2RUGDkquu+xV00PMVTr57s2QoMa_tYJ86YhThJ6c5bs1A@mail.gmail.com>
References: <CAAg5f2RUGDkquu+xV00PMVTr57s2QoMa_tYJ86YhThJ6c5bs1A@mail.gmail.com>
Message-ID: <CAPXQee5dvL8_mDKazz=rtsXkaffEGQbm04_=Jeekp4W+oFBoOQ@mail.gmail.com>

Thanks.

The plan is to have testing ready by the end of this week. At this moment,
I can confirm that integration tests have passed and we are doing
performing manual verification on the devices.

Cheers,

Karel

On Mon, Aug 17, 2015 at 8:28 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hello,
>
> since we had a few issues found and serious changes on the underlying DB
> schema (see Karel's mail), here is the staging of another beta:
>
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6332/
>
>
>
> Idea is to afterwards have a stable time of a week, and get the
> 1.1.0.Final, finally out!
>
> Any comments?
>
> -Matthias
>
>
> On Wed, Aug 12, 2015 at 8:52 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> Yes, I will discard the current staged release.
>> Thanks Erik for reporting these issues.
>>
>>
>>
>> On Tue, Aug 11, 2015 at 10:39 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> I think this is aldo worth to be included to 1.1.0.Final
>>>
>>>
>>> On Tuesday, August 11, 2015, Erik Jan de Wit <edewit at redhat.com> wrote:
>>>
>>>> I found these issues:
>>>>
>>>>
>>>>    1. AGPUSH-1492 <https://issues.jboss.org/browse/AGPUSH-1492> Deleting
>>>>    an Application leaves installations
>>>>    2.
>>>>       1.
>>>>          1. AGPUSH-1491 <https://issues.jboss.org/browse/AGPUSH-1491> Android
>>>>          doesn't show installations
>>>>
>>>>
>>>> On Tue, Aug 11, 2015 at 1:06 PM, Matthias Wessendorf <matzew at apache.org
>>>> > wrote:
>>>>
>>>>> looking...
>>>>>
>>>>> On Fri, Aug 7, 2015 at 3:48 PM, Sebastien Blanc <scm.blanc at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi team,
>>>>>>
>>>>>> I'm happy to announce that UPS 1.1.0 Final has been staged.
>>>>>>
>>>>>> Please test the staged release :
>>>>>>
>>>>>>
>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6277
>>>>>>
>>>>>> On Wednesday I'd like to press the button to release it to the wild.
>>>>>>
>>>>>> Sebi
>>>>>>
>>>>>> ps : the openshift update will follow
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>
>>>
>>>
>>> --
>>> Sent from Gmail Mobile
>>>
>>> _______________________________________________
>>> 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/20150819/01c00488/attachment-0001.html 

From thradec at gmail.com  Wed Aug 19 03:54:45 2015
From: thradec at gmail.com (=?UTF-8?B?VG9tw6HFoSBIcmFkZWM=?=)
Date: Wed, 19 Aug 2015 09:54:45 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.0-beta.4 (was: Re: Staging of
 UPS 1.1.0.Final)
In-Reply-To: <CAPXQee5dvL8_mDKazz=rtsXkaffEGQbm04_=Jeekp4W+oFBoOQ@mail.gmail.com>
References: <CAAg5f2RUGDkquu+xV00PMVTr57s2QoMa_tYJ86YhThJ6c5bs1A@mail.gmail.com>
	<CAPXQee5dvL8_mDKazz=rtsXkaffEGQbm04_=Jeekp4W+oFBoOQ@mail.gmail.com>
Message-ID: <CAF_jaDSH7zFdfuthrAsZ7mQuVYpqoB6AUt0XeKuo6igMw9hBLA@mail.gmail.com>

Hi all

So far I found following issues (only the first seems critical)
https://issues.jboss.org/browse/AGPUSH-1502
https://issues.jboss.org/browse/AGPUSH-1503
https://issues.jboss.org/browse/AGPUSH-1504

For now, I tried it on Wildly 9.0.0.Final and EAP 6.4.2.GA with MySQL
database. Prepared Openshift cartridge is working fine. Testing on iOS
device with HelloWord quickstart went also well.

Regards
Tomas




2015-08-19 9:10 GMT+02:00 Karel Piwko <kpiwko at redhat.com>:

> Thanks.
>
> The plan is to have testing ready by the end of this week. At this moment,
> I can confirm that integration tests have passed and we are doing
> performing manual verification on the devices.
>
> Cheers,
>
> Karel
>
> On Mon, Aug 17, 2015 at 8:28 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hello,
>>
>> since we had a few issues found and serious changes on the underlying DB
>> schema (see Karel's mail), here is the staging of another beta:
>>
>>
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6332/
>>
>>
>>
>> Idea is to afterwards have a stable time of a week, and get the
>> 1.1.0.Final, finally out!
>>
>> Any comments?
>>
>> -Matthias
>>
>>
>> On Wed, Aug 12, 2015 at 8:52 AM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>> Yes, I will discard the current staged release.
>>> Thanks Erik for reporting these issues.
>>>
>>>
>>>
>>> On Tue, Aug 11, 2015 at 10:39 PM, Matthias Wessendorf <matzew at apache.org
>>> > wrote:
>>>
>>>> I think this is aldo worth to be included to 1.1.0.Final
>>>>
>>>>
>>>> On Tuesday, August 11, 2015, Erik Jan de Wit <edewit at redhat.com> wrote:
>>>>
>>>>> I found these issues:
>>>>>
>>>>>
>>>>>    1. AGPUSH-1492 <https://issues.jboss.org/browse/AGPUSH-1492> Deleting
>>>>>    an Application leaves installations
>>>>>    2.
>>>>>       1.
>>>>>          1. AGPUSH-1491 <https://issues.jboss.org/browse/AGPUSH-1491> Android
>>>>>          doesn't show installations
>>>>>
>>>>>
>>>>> On Tue, Aug 11, 2015 at 1:06 PM, Matthias Wessendorf <
>>>>> matzew at apache.org> wrote:
>>>>>
>>>>>> looking...
>>>>>>
>>>>>> On Fri, Aug 7, 2015 at 3:48 PM, Sebastien Blanc <scm.blanc at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi team,
>>>>>>>
>>>>>>> I'm happy to announce that UPS 1.1.0 Final has been staged.
>>>>>>>
>>>>>>> Please test the staged release :
>>>>>>>
>>>>>>>
>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6277
>>>>>>>
>>>>>>> On Wednesday I'd like to press the button to release it to the wild.
>>>>>>>
>>>>>>> Sebi
>>>>>>>
>>>>>>> ps : the openshift update will follow
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>
>>>>
>>>>
>>>> --
>>>> Sent from Gmail Mobile
>>>>
>>>> _______________________________________________
>>>> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150819/f6e43894/attachment.html 

From idel.pivnitskiy at gmail.com  Wed Aug 19 10:20:50 2015
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Wed, 19 Aug 2015 17:20:50 +0300
Subject: [aerogear-dev] A separate JIRA project for AeroGear WebPush
Message-ID: <CAN+BUJq_cZoPrALOecign-wkfya6t4raFqp6r0_QOVVg_Cur5A@mail.gmail.com>

Hi!

I'm going to create a few JIRA issues for AeroGear WebPush Server and Java
Client. So, I think that it would be reasonable to create a separate JIRA
project for all issues for WebPush.
WDYT?

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

From matzew at apache.org  Wed Aug 19 10:23:35 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 19 Aug 2015 16:23:35 +0200
Subject: [aerogear-dev] A separate JIRA project for AeroGear WebPush
In-Reply-To: <CAN+BUJq_cZoPrALOecign-wkfya6t4raFqp6r0_QOVVg_Cur5A@mail.gmail.com>
References: <CAN+BUJq_cZoPrALOecign-wkfya6t4raFqp6r0_QOVVg_Cur5A@mail.gmail.com>
Message-ID: <CAAg5f2QE9YLOYQvqDsA8zZ=huoAT9T_=EhCKnyR4AznXdh568w@mail.gmail.com>

-1

let's stick w/ AGPUSH and use components and versions there.

On Wed, Aug 19, 2015 at 4:20 PM, Idel Pivnitskiy <idel.pivnitskiy at gmail.com>
wrote:

> Hi!
>
> I'm going to create a few JIRA issues for AeroGear WebPush Server and Java
> Client. So, I think that it would be reasonable to create a separate JIRA
> project for all issues for WebPush.
> WDYT?
>
> Best regards,
> Idel Pivnitskiy
> --
> E-mail: Idel.Pivnitskiy at gmail.com
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

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

From idel.pivnitskiy at gmail.com  Wed Aug 19 10:32:38 2015
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Wed, 19 Aug 2015 17:32:38 +0300
Subject: [aerogear-dev] A separate JIRA project for AeroGear WebPush
In-Reply-To: <CAAg5f2QE9YLOYQvqDsA8zZ=huoAT9T_=EhCKnyR4AznXdh568w@mail.gmail.com>
References: <CAN+BUJq_cZoPrALOecign-wkfya6t4raFqp6r0_QOVVg_Cur5A@mail.gmail.com>
	<CAAg5f2QE9YLOYQvqDsA8zZ=huoAT9T_=EhCKnyR4AznXdh568w@mail.gmail.com>
Message-ID: <CAN+BUJo5Dx26MDZ5tY_ATkTXx08mM2k8tAdK3jfncWo3umMgnw@mail.gmail.com>

Oh, yes, I see. Great!
Matthias, could you create a component for aerogear-webpush-java-client?

2015-08-19 17:23 GMT+03:00 Matthias Wessendorf <matzew at apache.org>:

> -1
>
> let's stick w/ AGPUSH and use components and versions there.
>
> On Wed, Aug 19, 2015 at 4:20 PM, Idel Pivnitskiy <
> idel.pivnitskiy at gmail.com> wrote:
>
>> Hi!
>>
>> I'm going to create a few JIRA issues for AeroGear WebPush Server and
>> Java Client. So, I think that it would be reasonable to create a separate
>> JIRA project for all issues for WebPush.
>> WDYT?
>>
>> Best regards,
>> Idel Pivnitskiy
>> --
>> E-mail: Idel.Pivnitskiy at gmail.com
>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Best regards,
Idel Pivnitskiy
E-mail: Idel.Pivnitskiy at gmail.com
Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150819/3efa8c4f/attachment-0001.html 

From idel.pivnitskiy at gmail.com  Wed Aug 19 10:34:54 2015
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Wed, 19 Aug 2015 17:34:54 +0300
Subject: [aerogear-dev] A separate JIRA project for AeroGear WebPush
In-Reply-To: <CAN+BUJo5Dx26MDZ5tY_ATkTXx08mM2k8tAdK3jfncWo3umMgnw@mail.gmail.com>
References: <CAN+BUJq_cZoPrALOecign-wkfya6t4raFqp6r0_QOVVg_Cur5A@mail.gmail.com>
	<CAAg5f2QE9YLOYQvqDsA8zZ=huoAT9T_=EhCKnyR4AznXdh568w@mail.gmail.com>
	<CAN+BUJo5Dx26MDZ5tY_ATkTXx08mM2k8tAdK3jfncWo3umMgnw@mail.gmail.com>
Message-ID: <CAN+BUJoC+3Hj4kYz5qyYJ_RswQeFbTJb0vZsPFa523twG41egA@mail.gmail.com>

And what is the difference between WebPush
<https://issues.jboss.org/browse/AGPUSH/component/12321047> and
WebPush-Server <https://issues.jboss.org/browse/AGPUSH/component/12321048>
 components?

2015-08-19 17:32 GMT+03:00 Idel Pivnitskiy <idel.pivnitskiy at gmail.com>:

> Oh, yes, I see. Great!
> Matthias, could you create a component for aerogear-webpush-java-client?
>
> 2015-08-19 17:23 GMT+03:00 Matthias Wessendorf <matzew at apache.org>:
>
>> -1
>>
>> let's stick w/ AGPUSH and use components and versions there.
>>
>> On Wed, Aug 19, 2015 at 4:20 PM, Idel Pivnitskiy <
>> idel.pivnitskiy at gmail.com> wrote:
>>
>>> Hi!
>>>
>>> I'm going to create a few JIRA issues for AeroGear WebPush Server and
>>> Java Client. So, I think that it would be reasonable to create a separate
>>> JIRA project for all issues for WebPush.
>>> WDYT?
>>>
>>> Best regards,
>>> Idel Pivnitskiy
>>> --
>>> E-mail: Idel.Pivnitskiy at gmail.com
>>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>>> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Best regards,
> Idel Pivnitskiy
> E-mail: Idel.Pivnitskiy at gmail.com
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>



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

From daniel.bevenius at gmail.com  Fri Aug 21 00:05:48 2015
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Fri, 21 Aug 2015 06:05:48 +0200
Subject: [aerogear-dev] WebPush Server supports the latest
	draft-ietf-webpush-protocol-00
In-Reply-To: <CAN+BUJo_KOjgdeQh3Yz98raGSnXrbiMrZSc4tZ_n=9x2YA+AQw@mail.gmail.com>
References: <CAN+BUJo_KOjgdeQh3Yz98raGSnXrbiMrZSc4tZ_n=9x2YA+AQw@mail.gmail.com>
Message-ID: <CAFJm-3GbbYDNhZXvrqcXnwAX7eNh=LVFoRoNH+Md0gb4m10_LA@mail.gmail.com>

Hi Idel,

great work on this. I've not tried out the WebPush Console yet but taken a
look at the server side and like what I've seen. Will hopefully be able to
take a look at the console next week.

Thanks,

/Dan

On 15 August 2015 at 04:09, Idel Pivnitskiy <idel.pivnitskiy at gmail.com>
wrote:

> Hi all!
>
> I'm happy to announce, that you are able to play with the latest draft of
> WebPush protocol. Our WebPush Server and Console are updated now. The new
> draft has too many changes, try it :)
>
> For more information, see
> https://github.com/aerogear/aerogear-webpush-server/pull/14
>
> Best regards,
> Idel Pivnitskiy
> --
> E-mail: Idel.Pivnitskiy at gmail.com
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150821/5b6ab533/attachment.html 

From artur.dryomov at gmail.com  Fri Aug 21 07:16:22 2015
From: artur.dryomov at gmail.com (Artur Dryomov)
Date: Fri, 21 Aug 2015 14:16:22 +0300
Subject: [aerogear-dev] Android Dependencies and DEX Size
Message-ID: <CAC6O=UW+dkB0jOd0N621AVCEkPF9uf16g=otMAX9CoT5Msxyiw@mail.gmail.com>

Hi everyone,

So, I?ve just hit the famous 65 K methods count and DEX error as a sweet
bonus while updating the application to latest Android 6.0-related
dependencies.

Long story short, I?ve analyzed [1] dependencies [2] for the Hawkular
Android Client [3]. Important notice?the application is not that big or
complicated.

Methods count is below.

   - Various dependencies: 2445.
   - Java & JavaX: 1684.
   - Android Support libraries: 12988.
   - Android: 3081.
   - Google Play Services: 22022.
   - Bouncycastle: 10423.
   - Spongycastle: 10423.
   - AeroGear: 1210.
   - Application itself: 1047.
   - Total: 65346.

This is kind of disappointing. Of course I can start to blame Android
Support libraries, but you clearly cannot develop apps these days without
using backports and helpers. Google Play Services is a bigger deal. It is a
dependency of the AeroGear Push module and you cannot live without it as
well, but you can use a modular dependency. I?ve addressed this in an issue
[4] which leads to another one [5]. It was fixed (there is Google Play
Services 7.8.0 already though), but not released. Bouncycastle and
Sprongycastle are related to security and are dependencies of the AeroGear
Store module which is a dependency of the AeroGear Authz module. I?m not
really sure I need this at all.

Let?s count again.

   - The current application: 65346 methods.
   - The application without Google Play Services and Castles: 22478.

The application can be (65346 ? 22478 = 2.9) times smaller.

What do you think about? Is there any chance to ditch these Castle
dependencies and release the new Push version?

Regards,
Artur.

[1]: http://inloop.github.io/apk-method-count
[2]: http://pastie.org/private/27y3igg4imyqfjvs9qz9a
[3]: https://github.com/hawkular/hawkular-android-client
[4]: https://issues.jboss.org/browse/AGDROID-432
[5]: https://issues.jboss.org/browse/AGDROID-351
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150821/db6fb663/attachment.html 

From dpassos at redhat.com  Fri Aug 21 07:33:32 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Fri, 21 Aug 2015 08:33:32 -0300
Subject: [aerogear-dev] Android Dependencies and DEX Size
In-Reply-To: <CAC6O=UW+dkB0jOd0N621AVCEkPF9uf16g=otMAX9CoT5Msxyiw@mail.gmail.com>
References: <CAC6O=UW+dkB0jOd0N621AVCEkPF9uf16g=otMAX9CoT5Msxyiw@mail.gmail.com>
Message-ID: <CADF=h2sA_zyqs9G463rg+Z28atREEsJBUC9JdZ1F9Ntn_PmufQ@mail.gmail.com>

Hi Artur,

Very nice report

On Fri, Aug 21, 2015 at 8:16 AM, Artur Dryomov <artur.dryomov at gmail.com>
wrote:

> Hi everyone,
>
> So, I?ve just hit the famous 65 K methods count and DEX error as a sweet
> bonus while updating the application to latest Android 6.0-related
> dependencies.
>
> Long story short, I?ve analyzed [1] dependencies [2] for the Hawkular
> Android Client [3]. Important notice?the application is not that big or
> complicated.
>
> Methods count is below.
>
>    - Various dependencies: 2445.
>    - Java & JavaX: 1684.
>    - Android Support libraries: 12988.
>    - Android: 3081.
>    - Google Play Services: 22022.
>    - Bouncycastle: 10423.
>    - Spongycastle: 10423.
>    - AeroGear: 1210.
>    - Application itself: 1047.
>    - Total: 65346.
>
> This is kind of disappointing. Of course I can start to blame Android
> Support libraries, but you clearly cannot develop apps these days without
> using backports and helpers. Google Play Services is a bigger deal. It is a
> dependency of the AeroGear Push module and you cannot live without it as
> well, but you can use a modular dependency. I?ve addressed this in an issue
> [4] which leads to another one [5]. It was fixed (there is Google Play
> Services 7.8.0 already though), but not released. Bouncycastle and
> Sprongycastle are related to security and are dependencies of the AeroGear
> Store module which is a dependency of the AeroGear Authz module. I?m not
> really sure I need this at all.
>

Unfortunately (or not) yes, you need this all.

TL;DR: Authz need a server token to communicate with the server, we need
store this token so, authz need store lib as dependency. This token need to
be stored encrypted so, store need security and castles. Makes sense?


>
> Let?s count again.
>
>    - The current application: 65346 methods.
>    - The application without Google Play Services and Castles: 22478.
>
> The application can be (65346 ? 22478 = 2.9) times smaller.
>
> What do you think about? Is there any chance to ditch these Castle
> dependencies and release the new Push version?
>

About push, we don't have plan to release the play module until version
3.0.0

Anyway you can fix the problem easily using multidex[1]

[1] https://developer.android.com/tools/building/multidex.html


>
> Regards,
> Artur.
>
> [1]: http://inloop.github.io/apk-method-count
> [2]: http://pastie.org/private/27y3igg4imyqfjvs9qz9a
> [3]: https://github.com/hawkular/hawkular-android-client
> [4]: https://issues.jboss.org/browse/AGDROID-432
> [5]: https://issues.jboss.org/browse/AGDROID-351
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150821/52ea3bdb/attachment-0001.html 

From artur.dryomov at gmail.com  Fri Aug 21 08:03:53 2015
From: artur.dryomov at gmail.com (Artur Dryomov)
Date: Fri, 21 Aug 2015 15:03:53 +0300
Subject: [aerogear-dev] Android Dependencies and DEX Size
In-Reply-To: <CADF=h2sA_zyqs9G463rg+Z28atREEsJBUC9JdZ1F9Ntn_PmufQ@mail.gmail.com>
References: <CAC6O=UW+dkB0jOd0N621AVCEkPF9uf16g=otMAX9CoT5Msxyiw@mail.gmail.com>
	<CADF=h2sA_zyqs9G463rg+Z28atREEsJBUC9JdZ1F9Ntn_PmufQ@mail.gmail.com>
Message-ID: <CAC6O=UUnvJ5ZM+Vw4p9ZO0RNSyd1nVX1X+=2eTszaWVN5B+M8w@mail.gmail.com>

Hey Daniel,

TL;DR: Authz need a server token to communicate with the server, we need
> store this token so, authz need store lib as dependency. This token need to
> be stored encrypted so, store need security and castles. Makes sense?


Totally, this can be seen at the dependency tree. Is it possible to use
something more simple for such purpose? The approach of consuming almost a
half of the DEX limit due to Store or (and) Security usage is kind of
suspicious. Android is a limiting environment already, using a single
dependency which has so many methods is strange. Include a Google Play
Services dependency without modules support and you don?t even have to
write an app, it will not compile already.

Not sure if it can help, but there is some sort of the repackaging project
for Castles [1].

About push, we don't have plan to release the play module until version
> 3.0.0


Is there any recent ETA on this?

Anyway you can fix the problem easily using multidex.


I know, but it is a questionable solution which cures symptoms instead of a
decease.

Artur.

[1]: https://rtyley.github.io/spongycastle/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150821/ffc2251c/attachment.html 

From matzew at apache.org  Mon Aug 24 09:22:33 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 24 Aug 2015 15:22:33 +0200
Subject: [aerogear-dev] Staging of UPS 1.1.0-beta.4 (was: Re: Staging of
 UPS 1.1.0.Final)
In-Reply-To: <CAF_jaDSH7zFdfuthrAsZ7mQuVYpqoB6AUt0XeKuo6igMw9hBLA@mail.gmail.com>
References: <CAAg5f2RUGDkquu+xV00PMVTr57s2QoMa_tYJ86YhThJ6c5bs1A@mail.gmail.com>
	<CAPXQee5dvL8_mDKazz=rtsXkaffEGQbm04_=Jeekp4W+oFBoOQ@mail.gmail.com>
	<CAF_jaDSH7zFdfuthrAsZ7mQuVYpqoB6AUt0XeKuo6igMw9hBLA@mail.gmail.com>
Message-ID: <CAAg5f2TocePZ3iui+QkVsEKsF61R3YwkaWmN6UUTPCJM6YGASQ@mail.gmail.com>

Ok, folks! I will move forward and release the shindig!

On Wed, Aug 19, 2015 at 9:54 AM, Tom?? Hradec <thradec at gmail.com> wrote:

> Hi all
>
> So far I found following issues (only the first seems critical)
> https://issues.jboss.org/browse/AGPUSH-1502
> https://issues.jboss.org/browse/AGPUSH-1503
> https://issues.jboss.org/browse/AGPUSH-1504
>
> For now, I tried it on Wildly 9.0.0.Final and EAP 6.4.2.GA with MySQL
> database. Prepared Openshift cartridge is working fine. Testing on iOS
> device with HelloWord quickstart went also well.
>
> Regards
> Tomas
>
>
>
>
> 2015-08-19 9:10 GMT+02:00 Karel Piwko <kpiwko at redhat.com>:
>
>> Thanks.
>>
>> The plan is to have testing ready by the end of this week. At this
>> moment, I can confirm that integration tests have passed and we are doing
>> performing manual verification on the devices.
>>
>> Cheers,
>>
>> Karel
>>
>> On Mon, Aug 17, 2015 at 8:28 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hello,
>>>
>>> since we had a few issues found and serious changes on the underlying DB
>>> schema (see Karel's mail), here is the staging of another beta:
>>>
>>>
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6332/
>>>
>>>
>>>
>>> Idea is to afterwards have a stable time of a week, and get the
>>> 1.1.0.Final, finally out!
>>>
>>> Any comments?
>>>
>>> -Matthias
>>>
>>>
>>> On Wed, Aug 12, 2015 at 8:52 AM, Sebastien Blanc <scm.blanc at gmail.com>
>>> wrote:
>>>
>>>> Yes, I will discard the current staged release.
>>>> Thanks Erik for reporting these issues.
>>>>
>>>>
>>>>
>>>> On Tue, Aug 11, 2015 at 10:39 PM, Matthias Wessendorf <
>>>> matzew at apache.org> wrote:
>>>>
>>>>> I think this is aldo worth to be included to 1.1.0.Final
>>>>>
>>>>>
>>>>> On Tuesday, August 11, 2015, Erik Jan de Wit <edewit at redhat.com>
>>>>> wrote:
>>>>>
>>>>>> I found these issues:
>>>>>>
>>>>>>
>>>>>>    1. AGPUSH-1492 <https://issues.jboss.org/browse/AGPUSH-1492> Deleting
>>>>>>    an Application leaves installations
>>>>>>    2.
>>>>>>       1.
>>>>>>          1. AGPUSH-1491 <https://issues.jboss.org/browse/AGPUSH-1491> Android
>>>>>>          doesn't show installations
>>>>>>
>>>>>>
>>>>>> On Tue, Aug 11, 2015 at 1:06 PM, Matthias Wessendorf <
>>>>>> matzew at apache.org> wrote:
>>>>>>
>>>>>>> looking...
>>>>>>>
>>>>>>> On Fri, Aug 7, 2015 at 3:48 PM, Sebastien Blanc <scm.blanc at gmail.com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Hi team,
>>>>>>>>
>>>>>>>> I'm happy to announce that UPS 1.1.0 Final has been staged.
>>>>>>>>
>>>>>>>> Please test the staged release :
>>>>>>>>
>>>>>>>>
>>>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6277
>>>>>>>>
>>>>>>>> On Wednesday I'd like to press the button to release it to the
>>>>>>>> wild.
>>>>>>>>
>>>>>>>> Sebi
>>>>>>>>
>>>>>>>> ps : the openshift update will follow
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sent from Gmail Mobile
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>
>
>
> _______________________________________________
> 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/20150824/bc63ba5b/attachment.html 

From lholmqui at redhat.com  Mon Aug 24 13:22:36 2015
From: lholmqui at redhat.com (Luke Holmquist)
Date: Mon, 24 Aug 2015 13:22:36 -0400
Subject: [aerogear-dev] UnifiedPush js client
Message-ID: <CALD3Fd3hq7ZV-gnuCq-w+7Kou6RRJeCh9K=oMxBXQ4D+Jd=03g@mail.gmail.com>

so i decided to take a gander at the push client lib in the aerogear.js
project.   Currently if someone would like to use it,  they have a couple
options.

1. download the whole lib,
2. download a custom build from the website
3. download a custom build from bower
4. create a custom build from source

In the past i think i was against breaking out pieces of the JS lib into
separate repo's since we could just use the AeroGearComponents repo i
created for custom builds.  But i think with the state of the JS lib(not
sure where it's going), it might make sense to, at least with the push
lib(perhaps the simplePush polyfill also) to break those out into separate
repo's similar to the other client projects.

I think the starting vision of the project has changed, so perhaps this
change is good.(this should probably be a whole separate thread)

Now that Chrome and Safari have push in the browser, FF is getting it also
very soon,  it's possible this part of the library will be used more


thoughts?

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

From matzew at apache.org  Mon Aug 24 13:45:35 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 24 Aug 2015 19:45:35 +0200
Subject: [aerogear-dev] UnifiedPush js client
In-Reply-To: <CALD3Fd3hq7ZV-gnuCq-w+7Kou6RRJeCh9K=oMxBXQ4D+Jd=03g@mail.gmail.com>
References: <CALD3Fd3hq7ZV-gnuCq-w+7Kou6RRJeCh9K=oMxBXQ4D+Jd=03g@mail.gmail.com>
Message-ID: <CAAg5f2QbZ+jU-QX-5scW_BTbwCyH=uJ+xgtmrRkxU1tr6DXGQg@mail.gmail.com>

On Mon, Aug 24, 2015 at 7:22 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> so i decided to take a gander at the push client lib in the aerogear.js
> project.   Currently if someone would like to use it,  they have a couple
> options.
>
> 1. download the whole lib,
> 2. download a custom build from the website
> 3. download a custom build from bower
> 4. create a custom build from source
>
> In the past i think i was against breaking out pieces of the JS lib into
> separate repo's since we could just use the AeroGearComponents repo i
> created for custom builds.  But i think with the state of the JS lib(not
> sure where it's going), it might make sense to, at least with the push
> lib(perhaps the simplePush polyfill also) to break those out into separate
> repo's similar to the other client projects.
>
> I think the starting vision of the project has changed, so perhaps this
> change is good.(this should probably be a whole separate thread)
>
> Now that Chrome and Safari have push in the browser, FF is getting it also
> very soon,  it's possible this part of the library will be used more
>
>
> thoughts?
>

yeah, makes sense to separate it.
And while getting back at the JS push lib, due to more interest in browser
based push, I think it would be good to revisit the security aspects, for
device (installation) registration against UPS.


>
> -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/20150824/1052bec5/attachment.html 

From lholmqui at redhat.com  Mon Aug 24 13:49:05 2015
From: lholmqui at redhat.com (Luke Holmquist)
Date: Mon, 24 Aug 2015 13:49:05 -0400
Subject: [aerogear-dev] UnifiedPush js client
In-Reply-To: <CAAg5f2QbZ+jU-QX-5scW_BTbwCyH=uJ+xgtmrRkxU1tr6DXGQg@mail.gmail.com>
References: <CALD3Fd3hq7ZV-gnuCq-w+7Kou6RRJeCh9K=oMxBXQ4D+Jd=03g@mail.gmail.com>
	<CAAg5f2QbZ+jU-QX-5scW_BTbwCyH=uJ+xgtmrRkxU1tr6DXGQg@mail.gmail.com>
Message-ID: <CALD3Fd2c8B-m9c45udeDcLmEx8gvW_0fgiL+19onR6spXaKEGA@mail.gmail.com>

On Mon, Aug 24, 2015 at 1:45 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Mon, Aug 24, 2015 at 7:22 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> so i decided to take a gander at the push client lib in the aerogear.js
>> project.   Currently if someone would like to use it,  they have a couple
>> options.
>>
>> 1. download the whole lib,
>> 2. download a custom build from the website
>> 3. download a custom build from bower
>> 4. create a custom build from source
>>
>> In the past i think i was against breaking out pieces of the JS lib into
>> separate repo's since we could just use the AeroGearComponents repo i
>> created for custom builds.  But i think with the state of the JS lib(not
>> sure where it's going), it might make sense to, at least with the push
>> lib(perhaps the simplePush polyfill also) to break those out into separate
>> repo's similar to the other client projects.
>>
>> I think the starting vision of the project has changed, so perhaps this
>> change is good.(this should probably be a whole separate thread)
>>
>> Now that Chrome and Safari have push in the browser, FF is getting it
>> also very soon,  it's possible this part of the library will be used more
>>
>>
>> thoughts?
>>
>
> yeah, makes sense to separate it.
> And while getting back at the JS push lib, due to more interest in browser
> based push, I think it would be good to revisit the security aspects, for
> device (installation) registration against UPS.
>
yea,  this is an issue.  Not sure the best way to approach this though.
 but thats a different conversation i think

>
>
>>
>> -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
>
> _______________________________________________
> 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/20150824/e99cc713/attachment.html 

From supittma at redhat.com  Mon Aug 24 14:19:04 2015
From: supittma at redhat.com (Summers Pittman)
Date: Mon, 24 Aug 2015 14:19:04 -0400
Subject: [aerogear-dev] SAML in Client libraries
Message-ID: <CAEQz2Ct=TeC7B8Z2uB=+d3Pee5MiQ041GZsY196=rvKTgzuUVw@mail.gmail.com>

So abstractj, corinnekrych, edewit, and I spoke this morning about adding
SAML support to the AeroGear client libraries.  This lead to a few
observations.

1 ) Mobile doesn't do SAML well (it is an OAuth 2 world)
2 ) SAML is VERY hard to set up and integrate with. (Multiple servers need
to exchange XML Metadata)
3 ) SAML was designed for hosted web applications, not for the RESTful
service web.  (You need at least two servers to have an application use
SAML)
4 ) There aren't many widely used SAML libraries for mobile.

>From these observations we made the follow decisions.

1 ) We will extend the authorization libraries to include some kind of
solution for SAML.  This will probably rely on a WebView and some form of
service broker to manage the authorization tokens.  Passport-saml and
KeyCloak both seem to have abilities in this area and we will begin our
investigation there.

2) We will create a docker image which will be a turn key SAML server to
test integration with.  Right now we are looking at using Shibboleth for
our service provider and identity provider.  Keycloak will be used for
communicating with the AG-SAML libraries initially.  Our goal, as always,
is to make our libraries as portable as possible.

3 ) We will provide some kind of server technology/integration plan to
serve as a template for adding mobile to existing SAML protected
applications.  This will be at the least documentation on aerogear.org and
at the most a docker app based on shibboleth's SAML server.

4 ) We will build some demo applications to showcase integrating with a
SAML provider.  Because SAML requires configuration on both the client and
ID servers our demo may have to be specific to services we can access or
host.  SAML makes the workflows to enable OAuth support look like child's
play.

What do you guys think?

Summers

PS Stay tuned for links to JIRAs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150824/e81e9d4f/attachment.html 

From matzew at apache.org  Mon Aug 24 14:34:04 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 24 Aug 2015 20:34:04 +0200
Subject: [aerogear-dev] UnifiedPush js client
In-Reply-To: <CALD3Fd2c8B-m9c45udeDcLmEx8gvW_0fgiL+19onR6spXaKEGA@mail.gmail.com>
References: <CALD3Fd3hq7ZV-gnuCq-w+7Kou6RRJeCh9K=oMxBXQ4D+Jd=03g@mail.gmail.com>
	<CAAg5f2QbZ+jU-QX-5scW_BTbwCyH=uJ+xgtmrRkxU1tr6DXGQg@mail.gmail.com>
	<CALD3Fd2c8B-m9c45udeDcLmEx8gvW_0fgiL+19onR6spXaKEGA@mail.gmail.com>
Message-ID: <CAAg5f2Q099BSY64wyeRjoQssMZCXyjfhgHWU3_jpuod=3G8ajQ@mail.gmail.com>

On Monday, August 24, 2015, Luke Holmquist <lholmqui at redhat.com> wrote:

>
>
> On Mon, Aug 24, 2015 at 1:45 PM, Matthias Wessendorf <matzew at apache.org
> <javascript:_e(%7B%7D,'cvml','matzew at apache.org');>> wrote:
>
>>
>>
>> On Mon, Aug 24, 2015 at 7:22 PM, Luke Holmquist <lholmqui at redhat.com
>> <javascript:_e(%7B%7D,'cvml','lholmqui at redhat.com');>> wrote:
>>
>>> so i decided to take a gander at the push client lib in the aerogear.js
>>> project.   Currently if someone would like to use it,  they have a couple
>>> options.
>>>
>>> 1. download the whole lib,
>>> 2. download a custom build from the website
>>> 3. download a custom build from bower
>>> 4. create a custom build from source
>>>
>>> In the past i think i was against breaking out pieces of the JS lib into
>>> separate repo's since we could just use the AeroGearComponents repo i
>>> created for custom builds.  But i think with the state of the JS lib(not
>>> sure where it's going), it might make sense to, at least with the push
>>> lib(perhaps the simplePush polyfill also) to break those out into separate
>>> repo's similar to the other client projects.
>>>
>>> I think the starting vision of the project has changed, so perhaps this
>>> change is good.(this should probably be a whole separate thread)
>>>
>>> Now that Chrome and Safari have push in the browser, FF is getting it
>>> also very soon,  it's possible this part of the library will be used more
>>>
>>>
>>> thoughts?
>>>
>>
>> yeah, makes sense to separate it.
>> And while getting back at the JS push lib, due to more interest in
>> browser based push, I think it would be good to revisit the security
>> aspects, for device (installation) registration against UPS.
>>
> yea,  this is an issue.  Not sure the best way to approach this though.
>  but thats a different conversation i think
>

yep


>
>>
>>>
>>> -Luke
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> <javascript:_e(%7B%7D,'cvml','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
>> <javascript:_e(%7B%7D,'cvml','aerogear-dev at lists.jboss.org');>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>

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

From bruno at abstractj.org  Mon Aug 24 15:13:34 2015
From: bruno at abstractj.org (Bruno Oliveira)
Date: Mon, 24 Aug 2015 16:13:34 -0300
Subject: [aerogear-dev] SAML in Client libraries
In-Reply-To: <CAEQz2Ct=TeC7B8Z2uB=+d3Pee5MiQ041GZsY196=rvKTgzuUVw@mail.gmail.com>
References: <CAEQz2Ct=TeC7B8Z2uB=+d3Pee5MiQ041GZsY196=rvKTgzuUVw@mail.gmail.com>
Message-ID: <CAM5SUC5-DUdy7r08j=oYA4H6JMWDtHBuGQQbhVHwd9Unizn6kA@mail.gmail.com>

+1, you nailed it

On Mon, Aug 24, 2015 at 3:19 PM, Summers Pittman <supittma at redhat.com>
wrote:

> So abstractj, corinnekrych, edewit, and I spoke this morning about adding
> SAML support to the AeroGear client libraries.  This lead to a few
> observations.
>
> 1 ) Mobile doesn't do SAML well (it is an OAuth 2 world)
> 2 ) SAML is VERY hard to set up and integrate with. (Multiple servers need
> to exchange XML Metadata)
> 3 ) SAML was designed for hosted web applications, not for the RESTful
> service web.  (You need at least two servers to have an application use
> SAML)
> 4 ) There aren't many widely used SAML libraries for mobile.
>
> From these observations we made the follow decisions.
>
> 1 ) We will extend the authorization libraries to include some kind of
> solution for SAML.  This will probably rely on a WebView and some form of
> service broker to manage the authorization tokens.  Passport-saml and
> KeyCloak both seem to have abilities in this area and we will begin our
> investigation there.
>
> 2) We will create a docker image which will be a turn key SAML server to
> test integration with.  Right now we are looking at using Shibboleth for
> our service provider and identity provider.  Keycloak will be used for
> communicating with the AG-SAML libraries initially.  Our goal, as always,
> is to make our libraries as portable as possible.
>
> 3 ) We will provide some kind of server technology/integration plan to
> serve as a template for adding mobile to existing SAML protected
> applications.  This will be at the least documentation on aerogear.org
> and at the most a docker app based on shibboleth's SAML server.
>
> 4 ) We will build some demo applications to showcase integrating with a
> SAML provider.  Because SAML requires configuration on both the client and
> ID servers our demo may have to be specific to services we can access or
> host.  SAML makes the workflows to enable OAuth support look like child's
> play.
>
> What do you guys think?
>
> Summers
>
> PS Stay tuned for links to JIRAs
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

-- 
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150824/5a9c9201/attachment.html 

From daniel.bevenius at gmail.com  Mon Aug 24 23:54:01 2015
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Tue, 25 Aug 2015 05:54:01 +0200
Subject: [aerogear-dev] SAML in Client libraries
In-Reply-To: <CAEQz2Ct=TeC7B8Z2uB=+d3Pee5MiQ041GZsY196=rvKTgzuUVw@mail.gmail.com>
References: <CAEQz2Ct=TeC7B8Z2uB=+d3Pee5MiQ041GZsY196=rvKTgzuUVw@mail.gmail.com>
Message-ID: <CAFJm-3HMZZ4gM3FE1+d8-MoBiUK=M1bXT14k-HqYLQVhEz78fQ@mail.gmail.com>

+1 Sounds good

On 24 August 2015 at 20:19, Summers Pittman <supittma at redhat.com> wrote:

> So abstractj, corinnekrych, edewit, and I spoke this morning about adding
> SAML support to the AeroGear client libraries.  This lead to a few
> observations.
>
> 1 ) Mobile doesn't do SAML well (it is an OAuth 2 world)
> 2 ) SAML is VERY hard to set up and integrate with. (Multiple servers need
> to exchange XML Metadata)
> 3 ) SAML was designed for hosted web applications, not for the RESTful
> service web.  (You need at least two servers to have an application use
> SAML)
> 4 ) There aren't many widely used SAML libraries for mobile.
>
> From these observations we made the follow decisions.
>
> 1 ) We will extend the authorization libraries to include some kind of
> solution for SAML.  This will probably rely on a WebView and some form of
> service broker to manage the authorization tokens.  Passport-saml and
> KeyCloak both seem to have abilities in this area and we will begin our
> investigation there.
>
> 2) We will create a docker image which will be a turn key SAML server to
> test integration with.  Right now we are looking at using Shibboleth for
> our service provider and identity provider.  Keycloak will be used for
> communicating with the AG-SAML libraries initially.  Our goal, as always,
> is to make our libraries as portable as possible.
>
> 3 ) We will provide some kind of server technology/integration plan to
> serve as a template for adding mobile to existing SAML protected
> applications.  This will be at the least documentation on aerogear.org
> and at the most a docker app based on shibboleth's SAML server.
>
> 4 ) We will build some demo applications to showcase integrating with a
> SAML provider.  Because SAML requires configuration on both the client and
> ID servers our demo may have to be specific to services we can access or
> host.  SAML makes the workflows to enable OAuth support look like child's
> play.
>
> What do you guys think?
>
> Summers
>
> PS Stay tuned for links to JIRAs
>
> _______________________________________________
> 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/20150825/a5ee2d96/attachment.html 

From matzew at apache.org  Tue Aug 25 02:49:53 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 25 Aug 2015 08:49:53 +0200
Subject: [aerogear-dev] SAML in Client libraries
In-Reply-To: <CAEQz2Ct=TeC7B8Z2uB=+d3Pee5MiQ041GZsY196=rvKTgzuUVw@mail.gmail.com>
References: <CAEQz2Ct=TeC7B8Z2uB=+d3Pee5MiQ041GZsY196=rvKTgzuUVw@mail.gmail.com>
Message-ID: <CAAg5f2Tqc3KjXuznSQ-0fi3aOEYgjqLQnJe7vvsutWWup1=UCA@mail.gmail.com>

On Mon, Aug 24, 2015 at 8:19 PM, Summers Pittman <supittma at redhat.com>
wrote:

> So abstractj, corinnekrych, edewit, and I spoke this morning about adding
> SAML support to the AeroGear client libraries.  This lead to a few
> observations.
>
> 1 ) Mobile doesn't do SAML well (it is an OAuth 2 world)
> 2 ) SAML is VERY hard to set up and integrate with. (Multiple servers need
> to exchange XML Metadata)
> 3 ) SAML was designed for hosted web applications, not for the RESTful
> service web.  (You need at least two servers to have an application use
> SAML)
> 4 ) There aren't many widely used SAML libraries for mobile.
>
> From these observations we made the follow decisions.
>
> 1 ) We will extend the authorization libraries to include some kind of
> solution for SAML.  This will probably rely on a WebView and some form of
> service broker to manage the authorization tokens.  Passport-saml and
> KeyCloak both seem to have abilities in this area and we will begin our
> investigation there.
>

+1000 on making this extra (ag-smal) libs!


>
> 2) We will create a docker image which will be a turn key SAML server to
> test integration with.  Right now we are looking at using Shibboleth for
> our service provider and identity provider.  Keycloak will be used for
> communicating with the AG-SAML libraries initially.  Our goal, as always,
> is to make our libraries as portable as possible.
>

+1

>
> 3 ) We will provide some kind of server technology/integration plan to
> serve as a template for adding mobile to existing SAML protected
> applications.  This will be at the least documentation on aerogear.org
> and at the most a docker app based on shibboleth's SAML server.
>

awesome!


>
> 4 ) We will build some demo applications to showcase integrating with a
> SAML provider.  Because SAML requires configuration on both the client and
> ID servers our demo may have to be specific to services we can access or
> host.  SAML makes the workflows to enable OAuth support look like child's
> play.
>

:-)


>
> What do you guys think?
>

sounds good to me, thanks for the updates!


>
> Summers
>
> PS Stay tuned for links to JIRAs
>
> _______________________________________________
> 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/20150825/f0061a02/attachment.html 

From matzew at apache.org  Tue Aug 25 08:13:09 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 25 Aug 2015 14:13:09 +0200
Subject: [aerogear-dev] UPS 1.1.0-beta.4 and Openshift release (was: Re:
 Staging of UPS 1.1.0-beta.4 (was: Re: Staging of UPS 1.1.0.Final))
Message-ID: <CAAg5f2QjCy3sjDAQ4C2B-XX=oaFh5eTF2t_cyReWZOzXxZ-pPg@mail.gmail.com>

Hello folks!

On our way to 1.1.0.Final, we have released another beta release! This
release contains changes to the DB schema and other small improvements.

List of JIRAs
https://issues.jboss.org/browse/AGPUSH/fixforversion/12327878

The release has been uploaded to Maven Central:
http://search.maven.org/#search%7Cga%7C1%7Cunifiedpush

It's, as usually, available on github too:
https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.1.0-beta.4


Openshift update:

As we move towards 1.1.0, the Openshift cartridge has been updated too, the
new beta 4 is available on Openshift:
https://github.com/aerogear/openshift-origin-cartridge-aerogear-push#installation

Greetings,
Matthias

On Mon, Aug 17, 2015 at 8:28 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hello,
>
> since we had a few issues found and serious changes on the underlying DB
> schema (see Karel's mail), here is the staging of another beta:
>
>
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6332/
>
>
>
> Idea is to afterwards have a stable time of a week, and get the
> 1.1.0.Final, finally out!
>
> Any comments?
>
> -Matthias
>
>
> On Wed, Aug 12, 2015 at 8:52 AM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>> Yes, I will discard the current staged release.
>> Thanks Erik for reporting these issues.
>>
>>
>>
>> On Tue, Aug 11, 2015 at 10:39 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> I think this is aldo worth to be included to 1.1.0.Final
>>>
>>>
>>> On Tuesday, August 11, 2015, Erik Jan de Wit <edewit at redhat.com> wrote:
>>>
>>>> I found these issues:
>>>>
>>>>
>>>>    1. AGPUSH-1492 <https://issues.jboss.org/browse/AGPUSH-1492> Deleting
>>>>    an Application leaves installations
>>>>    2.
>>>>       1.
>>>>          1. AGPUSH-1491 <https://issues.jboss.org/browse/AGPUSH-1491> Android
>>>>          doesn't show installations
>>>>
>>>>
>>>> On Tue, Aug 11, 2015 at 1:06 PM, Matthias Wessendorf <matzew at apache.org
>>>> > wrote:
>>>>
>>>>> looking...
>>>>>
>>>>> On Fri, Aug 7, 2015 at 3:48 PM, Sebastien Blanc <scm.blanc at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi team,
>>>>>>
>>>>>> I'm happy to announce that UPS 1.1.0 Final has been staged.
>>>>>>
>>>>>> Please test the staged release :
>>>>>>
>>>>>>
>>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6277
>>>>>>
>>>>>> On Wednesday I'd like to press the button to release it to the wild.
>>>>>>
>>>>>> Sebi
>>>>>>
>>>>>> ps : the openshift update will follow
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>
>>>
>>>
>>> --
>>> Sent from Gmail Mobile
>>>
>>> _______________________________________________
>>> 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/20150825/e299cd80/attachment-0001.html 

From dpassos at redhat.com  Tue Aug 25 08:26:15 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Tue, 25 Aug 2015 09:26:15 -0300
Subject: [aerogear-dev] AeroGear Android Push 2.2.2 Release
Message-ID: <CADF=h2u38GKYWLD0b1deo2VFjQHnHhUnoSPD0K7W6_c+FyKwow@mail.gmail.com>

Hey Guys,

We found a bug in our AeroGear Android Push library. It was fixed and
staged[1]

What is new in this version?

   - AGDROID-492 <https://issues.jboss.org/browse/AGDROID-492> - Categories
   field not working

We?re planning to release it tomorrow (Wednesday) in the end of the day.

Fell free to test it and let us know if you find any issues.

[1]
https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6402/
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150825/541096cc/attachment.html 

From dpassos at redhat.com  Tue Aug 25 19:01:29 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Tue, 25 Aug 2015 20:01:29 -0300
Subject: [aerogear-dev] Android Dependencies and DEX Size
In-Reply-To: <CAC6O=UUnvJ5ZM+Vw4p9ZO0RNSyd1nVX1X+=2eTszaWVN5B+M8w@mail.gmail.com>
References: <CAC6O=UW+dkB0jOd0N621AVCEkPF9uf16g=otMAX9CoT5Msxyiw@mail.gmail.com>
	<CADF=h2sA_zyqs9G463rg+Z28atREEsJBUC9JdZ1F9Ntn_PmufQ@mail.gmail.com>
	<CAC6O=UUnvJ5ZM+Vw4p9ZO0RNSyd1nVX1X+=2eTszaWVN5B+M8w@mail.gmail.com>
Message-ID: <CADF=h2v_d77e61nugCEFMPJRn9-aU8rse-NSONCtqkwbwUadwQ@mail.gmail.com>

On Fri, Aug 21, 2015 at 9:03 AM, Artur Dryomov <artur.dryomov at gmail.com>
wrote:

> Hey Daniel,
>
> TL;DR: Authz need a server token to communicate with the server, we need
>> store this token so, authz need store lib as dependency. This token need to
>> be stored encrypted so, store need security and castles. Makes sense?
>
>
> Totally, this can be seen at the dependency tree. Is it possible to use
> something more simple for such purpose? The approach of consuming almost a
> half of the DEX limit due to Store or (and) Security usage is kind of
> suspicious. Android is a limiting environment already, using a single
> dependency which has so many methods is strange. Include a Google Play
> Services dependency without modules support and you don?t even have to
> write an app, it will not compile already.
>

The only think we have in mind for now is add some proguard[1] in our libs,
but we are always open for new ideas.


> Not sure if it can help, but there is some sort of the repackaging project
> for Castles [1].
>

I'll take a look at it with Bruno and do some tests.


> About push, we don't have plan to release the play module until version
>> 3.0.0
>
>
> Is there any recent ETA on this?
>

Yes, schedule for October with UPS 1.2[2]


> Anyway you can fix the problem easily using multidex.
>
>
> I know, but it is a questionable solution which cures symptoms instead of
> a decease.
>
> Artur.
>
> [1]: https://rtyley.github.io/spongycastle/
>

[1] https://issues.jboss.org/browse/AGDROID-408
[2]
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-RFC-future-Roadmap-for-Unified-Push-Server-td11888.html

_______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150825/84ead37a/attachment.html 

From matzew at apache.org  Wed Aug 26 02:31:10 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 26 Aug 2015 08:31:10 +0200
Subject: [aerogear-dev] [Aerogear-users] AeroGear Android Push 2.2.2
	Release
In-Reply-To: <CADF=h2u38GKYWLD0b1deo2VFjQHnHhUnoSPD0K7W6_c+FyKwow@mail.gmail.com>
References: <CADF=h2u38GKYWLD0b1deo2VFjQHnHhUnoSPD0K7W6_c+FyKwow@mail.gmail.com>
Message-ID: <CAAg5f2RCyXVwq9JVBQJSvt4q3bNOu5kRe-nrHrNQJpwAEAYJ6Q@mail.gmail.com>

+1



On Tue, Aug 25, 2015 at 2:26 PM, Daniel Passos <dpassos at redhat.com> wrote:

> Hey Guys,
>
> We found a bug in our AeroGear Android Push library. It was fixed and
> staged[1]
>
> What is new in this version?
>
>    - AGDROID-492 <https://issues.jboss.org/browse/AGDROID-492> -
>    Categories field not working
>
> We?re planning to release it tomorrow (Wednesday) in the end of the day.
>
> Fell free to test it and let us know if you find any issues.
>
> [1]
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6402/
> ?
>
> _______________________________________________
> 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/20150826/01cd9e18/attachment.html 

From edewit at redhat.com  Wed Aug 26 02:55:27 2015
From: edewit at redhat.com (Erik Jan de Wit)
Date: Wed, 26 Aug 2015 08:55:27 +0200
Subject: [aerogear-dev] [Aerogear-users] AeroGear Android Push 2.2.2
	Release
In-Reply-To: <CADF=h2u38GKYWLD0b1deo2VFjQHnHhUnoSPD0K7W6_c+FyKwow@mail.gmail.com>
References: <CADF=h2u38GKYWLD0b1deo2VFjQHnHhUnoSPD0K7W6_c+FyKwow@mail.gmail.com>
Message-ID: <CAO2B-fbJA4nGra8j9fsKgEpWOGL--aBH13UfWbGHwZ3q=mTvUQ@mail.gmail.com>

Hot on the heels of the AeroGear Android Push library we also plan to
update the cordova push plugin because we have the same issue AGCORDOVA-112
<https://issues.jboss.org/browse/AGCORDOVA-112>. After the release on
Wednesday I'll update the plugin and stage that.

On Tue, Aug 25, 2015 at 2:26 PM, Daniel Passos <dpassos at redhat.com> wrote:

> Hey Guys,
>
> We found a bug in our AeroGear Android Push library. It was fixed and
> staged[1]
>
> What is new in this version?
>
>    - AGDROID-492 <https://issues.jboss.org/browse/AGDROID-492> -
>    Categories field not working
>
> We?re planning to release it tomorrow (Wednesday) in the end of the day.
>
> Fell free to test it and let us know if you find any issues.
>
> [1]
> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6402/
> ?
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>


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

From matzew at apache.org  Wed Aug 26 03:48:05 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 26 Aug 2015 09:48:05 +0200
Subject: [aerogear-dev] [Aerogear-users] AeroGear Android Push 2.2.2
	Release
In-Reply-To: <CAO2B-fbJA4nGra8j9fsKgEpWOGL--aBH13UfWbGHwZ3q=mTvUQ@mail.gmail.com>
References: <CADF=h2u38GKYWLD0b1deo2VFjQHnHhUnoSPD0K7W6_c+FyKwow@mail.gmail.com>
	<CAO2B-fbJA4nGra8j9fsKgEpWOGL--aBH13UfWbGHwZ3q=mTvUQ@mail.gmail.com>
Message-ID: <CAAg5f2TqVvP2Gt88_U6yCVV8nvpDW17ubhZUy5pav3UuJ4-ZCQ@mail.gmail.com>

yay!

On Wed, Aug 26, 2015 at 8:55 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hot on the heels of the AeroGear Android Push library we also plan to
> update the cordova push plugin because we have the same issue
> AGCORDOVA-112 <https://issues.jboss.org/browse/AGCORDOVA-112>. After the
> release on Wednesday I'll update the plugin and stage that.
>
> On Tue, Aug 25, 2015 at 2:26 PM, Daniel Passos <dpassos at redhat.com> wrote:
>
>> Hey Guys,
>>
>> We found a bug in our AeroGear Android Push library. It was fixed and
>> staged[1]
>>
>> What is new in this version?
>>
>>    - AGDROID-492 <https://issues.jboss.org/browse/AGDROID-492> -
>>    Categories field not working
>>
>> We?re planning to release it tomorrow (Wednesday) in the end of the day.
>>
>> Fell free to test it and let us know if you find any issues.
>>
>> [1]
>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6402/
>> ?
>>
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>
>
> --
> Cheers,
>        Erik Jan
>
> _______________________________________________
> 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/20150826/cea3a4b7/attachment-0001.html 

From dpassos at redhat.com  Thu Aug 27 13:37:15 2015
From: dpassos at redhat.com (Daniel Passos)
Date: Thu, 27 Aug 2015 14:37:15 -0300
Subject: [aerogear-dev] [Aerogear-users] AeroGear Android Push 2.2.2
	Release
In-Reply-To: <CAAg5f2TqVvP2Gt88_U6yCVV8nvpDW17ubhZUy5pav3UuJ4-ZCQ@mail.gmail.com>
References: <CADF=h2u38GKYWLD0b1deo2VFjQHnHhUnoSPD0K7W6_c+FyKwow@mail.gmail.com>
	<CAO2B-fbJA4nGra8j9fsKgEpWOGL--aBH13UfWbGHwZ3q=mTvUQ@mail.gmail.com>
	<CAAg5f2TqVvP2Gt88_U6yCVV8nvpDW17ubhZUy5pav3UuJ4-ZCQ@mail.gmail.com>
Message-ID: <CADF=h2v9K_co4dPWbGwkJtBnaUYjwYzKQAO-oFNtz8Yy5mgZig@mail.gmail.com>

Just clicked on release button :)

On Wed, Aug 26, 2015 at 4:48 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> yay!
>
> On Wed, Aug 26, 2015 at 8:55 AM, Erik Jan de Wit <edewit at redhat.com>
> wrote:
>
>> Hot on the heels of the AeroGear Android Push library we also plan to
>> update the cordova push plugin because we have the same issue
>> AGCORDOVA-112 <https://issues.jboss.org/browse/AGCORDOVA-112>. After the
>> release on Wednesday I'll update the plugin and stage that.
>>
>> On Tue, Aug 25, 2015 at 2:26 PM, Daniel Passos <dpassos at redhat.com>
>> wrote:
>>
>>> Hey Guys,
>>>
>>> We found a bug in our AeroGear Android Push library. It was fixed and
>>> staged[1]
>>>
>>> What is new in this version?
>>>
>>>    - AGDROID-492 <https://issues.jboss.org/browse/AGDROID-492> -
>>>    Categories field not working
>>>
>>> We?re planning to release it tomorrow (Wednesday) in the end of the day.
>>>
>>> Fell free to test it and let us know if you find any issues.
>>>
>>> [1]
>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6402/
>>> ?
>>>
>>> _______________________________________________
>>> Aerogear-users mailing list
>>> Aerogear-users at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>>
>>>
>>
>>
>> --
>> Cheers,
>>        Erik Jan
>>
>> _______________________________________________
>> 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
>
>


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

From lukas at fryc.eu  Mon Aug 31 04:55:16 2015
From: lukas at fryc.eu (=?UTF-8?B?THVrw6HFoSBGcnnEjQ==?=)
Date: Mon, 31 Aug 2015 10:55:16 +0200
Subject: [aerogear-dev] UnifiedPush js client
In-Reply-To: <CALD3Fd3hq7ZV-gnuCq-w+7Kou6RRJeCh9K=oMxBXQ4D+Jd=03g@mail.gmail.com>
References: <CALD3Fd3hq7ZV-gnuCq-w+7Kou6RRJeCh9K=oMxBXQ4D+Jd=03g@mail.gmail.com>
Message-ID: <CAEroY36u6bZx+teP_u5goD4JcO6wo9pDp=f2JxEvDkeEw97RkQ@mail.gmail.com>

You are right Luke, this start to make more and more sense :-)

On Mon, Aug 24, 2015 at 7:22 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> so i decided to take a gander at the push client lib in the aerogear.js
> project.   Currently if someone would like to use it,  they have a couple
> options.
>
> 1. download the whole lib,
> 2. download a custom build from the website
> 3. download a custom build from bower
> 4. create a custom build from source
>
> In the past i think i was against breaking out pieces of the JS lib into
> separate repo's since we could just use the AeroGearComponents repo i
> created for custom builds.  But i think with the state of the JS lib(not
> sure where it's going), it might make sense to, at least with the push
> lib(perhaps the simplePush polyfill also) to break those out into separate
> repo's similar to the other client projects.
>
> I think the starting vision of the project has changed, so perhaps this
> change is good.(this should probably be a whole separate thread)
>
> Now that Chrome and Safari have push in the browser, FF is getting it also
> very soon,  it's possible this part of the library will be used more
>
>
> thoughts?
>
> -Luke
>
> _______________________________________________
> 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/20150831/3bc9a66b/attachment.html 

From corinnekrych at gmail.com  Mon Aug 31 05:11:22 2015
From: corinnekrych at gmail.com (Corinne Krych)
Date: Mon, 31 Aug 2015 11:11:22 +0200
Subject: [aerogear-dev] UnifiedPush js client
In-Reply-To: <CAEroY36u6bZx+teP_u5goD4JcO6wo9pDp=f2JxEvDkeEw97RkQ@mail.gmail.com>
References: <CALD3Fd3hq7ZV-gnuCq-w+7Kou6RRJeCh9K=oMxBXQ4D+Jd=03g@mail.gmail.com>
	<CAEroY36u6bZx+teP_u5goD4JcO6wo9pDp=f2JxEvDkeEw97RkQ@mail.gmail.com>
Message-ID: <CAL8vO=fMQe7mTmvVg6Q0tiVv15F6Z2-nGdpQF3afTVZZ2-SK0w@mail.gmail.com>

+1
This way, we're getting closer to native libs approach with separate libs

On 31 August 2015 at 10:55, Luk?? Fry? <lukas at fryc.eu> wrote:

> You are right Luke, this start to make more and more sense :-)
>
> On Mon, Aug 24, 2015 at 7:22 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> so i decided to take a gander at the push client lib in the aerogear.js
>> project.   Currently if someone would like to use it,  they have a couple
>> options.
>>
>> 1. download the whole lib,
>> 2. download a custom build from the website
>> 3. download a custom build from bower
>> 4. create a custom build from source
>>
>> In the past i think i was against breaking out pieces of the JS lib into
>> separate repo's since we could just use the AeroGearComponents repo i
>> created for custom builds.  But i think with the state of the JS lib(not
>> sure where it's going), it might make sense to, at least with the push
>> lib(perhaps the simplePush polyfill also) to break those out into separate
>> repo's similar to the other client projects.
>>
>> I think the starting vision of the project has changed, so perhaps this
>> change is good.(this should probably be a whole separate thread)
>>
>> Now that Chrome and Safari have push in the browser, FF is getting it
>> also very soon,  it's possible this part of the library will be used more
>>
>>
>> thoughts?
>>
>> -Luke
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150831/f1225d8e/attachment.html 

From lholmqui at redhat.com  Mon Aug 31 11:12:16 2015
From: lholmqui at redhat.com (Luke Holmquist)
Date: Mon, 31 Aug 2015 11:12:16 -0400
Subject: [aerogear-dev] SimplePush Polyfill work
Message-ID: <CALD3Fd3FazKgKHPCwb5Lo0qOO9jeJMmughG+Z7VvDC=SRgciBA@mail.gmail.com>

so now that WebPush is going to take over SimplePush, i'm thinking of
closing the related JIRA's that we have open for simple push in the AG-JS
instance.


Not that we've really done any work on it lately,  but it would be good to
clean this up a little.


Thoughts?


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

From scm.blanc at gmail.com  Mon Aug 31 11:17:50 2015
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 31 Aug 2015 17:17:50 +0200
Subject: [aerogear-dev] SimplePush Polyfill work
In-Reply-To: <CALD3Fd3FazKgKHPCwb5Lo0qOO9jeJMmughG+Z7VvDC=SRgciBA@mail.gmail.com>
References: <CALD3Fd3FazKgKHPCwb5Lo0qOO9jeJMmughG+Z7VvDC=SRgciBA@mail.gmail.com>
Message-ID: <CAD_dpu2jpyX0rnwAHyN0BmS3DvOf-hwBTfP0wZAn+RCZhK9VeQ@mail.gmail.com>

+1

On Mon, Aug 31, 2015 at 5:12 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> so now that WebPush is going to take over SimplePush, i'm thinking of
> closing the related JIRA's that we have open for simple push in the AG-JS
> instance.
>
>
> Not that we've really done any work on it lately,  but it would be good to
> clean this up a little.
>
>
> Thoughts?
>
>
> -Luke
>
> _______________________________________________
> 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/20150831/7262beb3/attachment-0001.html 

From lholmqui at redhat.com  Mon Aug 31 11:29:02 2015
From: lholmqui at redhat.com (Luke Holmquist)
Date: Mon, 31 Aug 2015 11:29:02 -0400
Subject: [aerogear-dev] UnifiedPush js client
In-Reply-To: <CAL8vO=fMQe7mTmvVg6Q0tiVv15F6Z2-nGdpQF3afTVZZ2-SK0w@mail.gmail.com>
References: <CALD3Fd3hq7ZV-gnuCq-w+7Kou6RRJeCh9K=oMxBXQ4D+Jd=03g@mail.gmail.com>
	<CAEroY36u6bZx+teP_u5goD4JcO6wo9pDp=f2JxEvDkeEw97RkQ@mail.gmail.com>
	<CAL8vO=fMQe7mTmvVg6Q0tiVv15F6Z2-nGdpQF3afTVZZ2-SK0w@mail.gmail.com>
Message-ID: <CALD3Fd2_aboC=+YbeusLO5es-w9B+nJ7xNd9hyhPf1MHXNBBQg@mail.gmail.com>

The new Repo is now here https://github.com/aerogear/aerogear-js-push !!

I'll create some JIRA's to update the Readme, update aerogear.org, remove
the code from the main repo, etc...


Question.  Will this require a major version bump once i remove the code?
 i'm thinking yes

On Mon, Aug 31, 2015 at 5:11 AM, Corinne Krych <corinnekrych at gmail.com>
wrote:

> +1
> This way, we're getting closer to native libs approach with separate libs
>
> On 31 August 2015 at 10:55, Luk?? Fry? <lukas at fryc.eu> wrote:
>
>> You are right Luke, this start to make more and more sense :-)
>>
>> On Mon, Aug 24, 2015 at 7:22 PM, Luke Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>> so i decided to take a gander at the push client lib in the aerogear.js
>>> project.   Currently if someone would like to use it,  they have a couple
>>> options.
>>>
>>> 1. download the whole lib,
>>> 2. download a custom build from the website
>>> 3. download a custom build from bower
>>> 4. create a custom build from source
>>>
>>> In the past i think i was against breaking out pieces of the JS lib into
>>> separate repo's since we could just use the AeroGearComponents repo i
>>> created for custom builds.  But i think with the state of the JS lib(not
>>> sure where it's going), it might make sense to, at least with the push
>>> lib(perhaps the simplePush polyfill also) to break those out into separate
>>> repo's similar to the other client projects.
>>>
>>> I think the starting vision of the project has changed, so perhaps this
>>> change is good.(this should probably be a whole separate thread)
>>>
>>> Now that Chrome and Safari have push in the browser, FF is getting it
>>> also very soon,  it's possible this part of the library will be used more
>>>
>>>
>>> thoughts?
>>>
>>> -Luke
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150831/134f8e15/attachment.html 

From matzew at apache.org  Mon Aug 31 12:01:02 2015
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 31 Aug 2015 18:01:02 +0200
Subject: [aerogear-dev] UnifiedPush js client
In-Reply-To: <CALD3Fd2_aboC=+YbeusLO5es-w9B+nJ7xNd9hyhPf1MHXNBBQg@mail.gmail.com>
References: <CALD3Fd3hq7ZV-gnuCq-w+7Kou6RRJeCh9K=oMxBXQ4D+Jd=03g@mail.gmail.com>
	<CAEroY36u6bZx+teP_u5goD4JcO6wo9pDp=f2JxEvDkeEw97RkQ@mail.gmail.com>
	<CAL8vO=fMQe7mTmvVg6Q0tiVv15F6Z2-nGdpQF3afTVZZ2-SK0w@mail.gmail.com>
	<CALD3Fd2_aboC=+YbeusLO5es-w9B+nJ7xNd9hyhPf1MHXNBBQg@mail.gmail.com>
Message-ID: <CAAg5f2TKsHs7vXikm36TSBS8RpDKjmwv=3DYgFYKwOaJpTYPvQ@mail.gmail.com>

sure, let's do it - makes it obvious something changed

On Mon, Aug 31, 2015 at 5:29 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> The new Repo is now here https://github.com/aerogear/aerogear-js-push !!
>
> I'll create some JIRA's to update the Readme, update aerogear.org, remove
> the code from the main repo, etc...
>
>
> Question.  Will this require a major version bump once i remove the code?
>  i'm thinking yes
>
> On Mon, Aug 31, 2015 at 5:11 AM, Corinne Krych <corinnekrych at gmail.com>
> wrote:
>
>> +1
>> This way, we're getting closer to native libs approach with separate libs
>>
>> On 31 August 2015 at 10:55, Luk?? Fry? <lukas at fryc.eu> wrote:
>>
>>> You are right Luke, this start to make more and more sense :-)
>>>
>>> On Mon, Aug 24, 2015 at 7:22 PM, Luke Holmquist <lholmqui at redhat.com>
>>> wrote:
>>>
>>>> so i decided to take a gander at the push client lib in the aerogear.js
>>>> project.   Currently if someone would like to use it,  they have a couple
>>>> options.
>>>>
>>>> 1. download the whole lib,
>>>> 2. download a custom build from the website
>>>> 3. download a custom build from bower
>>>> 4. create a custom build from source
>>>>
>>>> In the past i think i was against breaking out pieces of the JS lib
>>>> into separate repo's since we could just use the AeroGearComponents repo i
>>>> created for custom builds.  But i think with the state of the JS lib(not
>>>> sure where it's going), it might make sense to, at least with the push
>>>> lib(perhaps the simplePush polyfill also) to break those out into separate
>>>> repo's similar to the other client projects.
>>>>
>>>> I think the starting vision of the project has changed, so perhaps this
>>>> change is good.(this should probably be a whole separate thread)
>>>>
>>>> Now that Chrome and Safari have push in the browser, FF is getting it
>>>> also very soon,  it's possible this part of the library will be used more
>>>>
>>>>
>>>> thoughts?
>>>>
>>>> -Luke
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> 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/20150831/96a8fcb2/attachment.html 

From daniel.bevenius at gmail.com  Mon Aug 31 12:27:19 2015
From: daniel.bevenius at gmail.com (Daniel Bevenius)
Date: Mon, 31 Aug 2015 18:27:19 +0200
Subject: [aerogear-dev] SimplePush Polyfill work
In-Reply-To: <CAD_dpu2jpyX0rnwAHyN0BmS3DvOf-hwBTfP0wZAn+RCZhK9VeQ@mail.gmail.com>
References: <CALD3Fd3FazKgKHPCwb5Lo0qOO9jeJMmughG+Z7VvDC=SRgciBA@mail.gmail.com>
	<CAD_dpu2jpyX0rnwAHyN0BmS3DvOf-hwBTfP0wZAn+RCZhK9VeQ@mail.gmail.com>
Message-ID: <CAFJm-3GriFtaJdTkcU2WN8tiXOk1xjhG5732L+P6s6_RcY=k0Q@mail.gmail.com>

+1

m?ndag 31 augusti 2015 skrev Sebastien Blanc <scm.blanc at gmail.com>:

> +1
>
> On Mon, Aug 31, 2015 at 5:12 PM, Luke Holmquist <lholmqui at redhat.com
> <javascript:_e(%7B%7D,'cvml','lholmqui at redhat.com');>> wrote:
>
>> so now that WebPush is going to take over SimplePush, i'm thinking of
>> closing the related JIRA's that we have open for simple push in the AG-JS
>> instance.
>>
>>
>> Not that we've really done any work on it lately,  but it would be good
>> to clean this up a little.
>>
>>
>> Thoughts?
>>
>>
>> -Luke
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> <javascript:_e(%7B%7D,'cvml','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/20150831/35d5d8a3/attachment.html 

From idel.pivnitskiy at gmail.com  Mon Aug 31 15:45:49 2015
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Mon, 31 Aug 2015 22:45:49 +0300
Subject: [aerogear-dev] SimplePush Polyfill work
In-Reply-To: <CAFJm-3GriFtaJdTkcU2WN8tiXOk1xjhG5732L+P6s6_RcY=k0Q@mail.gmail.com>
References: <CALD3Fd3FazKgKHPCwb5Lo0qOO9jeJMmughG+Z7VvDC=SRgciBA@mail.gmail.com>
	<CAD_dpu2jpyX0rnwAHyN0BmS3DvOf-hwBTfP0wZAn+RCZhK9VeQ@mail.gmail.com>
	<CAFJm-3GriFtaJdTkcU2WN8tiXOk1xjhG5732L+P6s6_RcY=k0Q@mail.gmail.com>
Message-ID: <CAN+BUJpgd8PJjRbZV5ozWM0yzfUJh2ywRbMAoz4gmohxybtQRw@mail.gmail.com>

+1

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

On Mon, Aug 31, 2015 at 7:27 PM, Daniel Bevenius <daniel.bevenius at gmail.com>
wrote:

> +1
>
>
> m?ndag 31 augusti 2015 skrev Sebastien Blanc <scm.blanc at gmail.com>:
>
>> +1
>>
>> On Mon, Aug 31, 2015 at 5:12 PM, Luke Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>> so now that WebPush is going to take over SimplePush, i'm thinking of
>>> closing the related JIRA's that we have open for simple push in the AG-JS
>>> instance.
>>>
>>>
>>> Not that we've really done any work on it lately,  but it would be good
>>> to clean this up a little.
>>>
>>>
>>> Thoughts?
>>>
>>>
>>> -Luke
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150831/b2ae79ba/attachment-0001.html 

From jrconlin at gmail.com  Mon Aug 31 18:59:01 2015
From: jrconlin at gmail.com (JR Conlin)
Date: Mon, 31 Aug 2015 15:59:01 -0700
Subject: [aerogear-dev] SimplePush Polyfill work
In-Reply-To: <CAN+BUJpgd8PJjRbZV5ozWM0yzfUJh2ywRbMAoz4gmohxybtQRw@mail.gmail.com>
References: <CALD3Fd3FazKgKHPCwb5Lo0qOO9jeJMmughG+Z7VvDC=SRgciBA@mail.gmail.com>
	<CAD_dpu2jpyX0rnwAHyN0BmS3DvOf-hwBTfP0wZAn+RCZhK9VeQ@mail.gmail.com>
	<CAFJm-3GriFtaJdTkcU2WN8tiXOk1xjhG5732L+P6s6_RcY=k0Q@mail.gmail.com>
	<CAN+BUJpgd8PJjRbZV5ozWM0yzfUJh2ywRbMAoz4gmohxybtQRw@mail.gmail.com>
Message-ID: <55E4DC35.9020003@gmail.com>

+4

(sorry, just had some fun with a bounding issue, and felt like sharing.)

Just to let y'all know, we're going to be running SimplePush for a
while, mostly for older devices. One thing we discovered is that some
clients may have a LARGE number of old channels registered and sending
them as part of the Hello is a waste. (Our server doesn't pay attention
to them.) Newer clients may have an interim fix that blanks the
clientIDs:[] record.) Aside from that, we're definitely not going to be
pushing any changes that should impact your library.

We've not stood up a production WebPush server, partly because the data
encryption portion of the standard is still under discussion. For what
it's worth, there are also a few other discussion points that have yet
to be finalized (e.g. should developers register with servers, should
clients specify channels like they did for SimplePush, etc.) but the
data bit is the biggest obstacle.

As always, thanks so much for the continuing support.


On 8/31/2015 12:45 PM, Idel Pivnitskiy wrote:
> +1
>
> Best regards,
> Idel Pivnitskiy
> --
> E-mail: Idel.Pivnitskiy at gmail.com <mailto:Idel.Pivnitskiy at gmail.com>
> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>
> On Mon, Aug 31, 2015 at 7:27 PM, Daniel Bevenius
> <daniel.bevenius at gmail.com <mailto:daniel.bevenius at gmail.com>> wrote:
>
>     +1
>
>
>     m?ndag 31 augusti 2015 skrev Sebastien Blanc <scm.blanc at gmail.com
>     <mailto:scm.blanc at gmail.com>>:
>
>         +1
>
>         On Mon, Aug 31, 2015 at 5:12 PM, Luke Holmquist
>         <lholmqui at redhat.com> wrote:
>
>             so now that WebPush is going to take over SimplePush, i'm
>             thinking of closing the related JIRA's that we have open
>             for simple push in the AG-JS instance.
>
>
>             Not that we've really done any work on it lately,  but it
>             would be good to clean this up a little.
>
>
>             Thoughts?
>
>
>             -Luke
>
>             _______________________________________________
>             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 <mailto:aerogear-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

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