From lrossett at redhat.com  Thu Feb  2 07:31:10 2017
From: lrossett at redhat.com (Leonardo Rossetti)
Date: Thu, 2 Feb 2017 10:31:10 -0200
Subject: [aerogear-dev] ups admin ui
Message-ID: <CAF-nxa_aZK4fHWONXEokVdp1zbU29AOZsiME1iSB5SxxYzRUkQ@mail.gmail.com>

Hello,

Currently we have the UPS admin UI embedded into
aerogear-unifiedpush-server project/repository.

Could the admin-ui be a separated project (repository) with its own war
file?

While it may increase release process complexity (a new project
dependency), I think it brings some benefits to the table, such as having a
development cycle of this own, easier to write automated tests and easier
to attract contributors from the javascript community (since we would be
using common javascript tools to build it).

WDYT?

-- 
Leonardo Rossetti
lrossett at redhat.com
+55 11 99703 0621
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170202/17aeddb8/attachment.html 

From matzew at apache.org  Thu Feb  2 08:01:05 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 2 Feb 2017 14:01:05 +0100
Subject: [aerogear-dev] ups admin ui
In-Reply-To: <CAF-nxa_aZK4fHWONXEokVdp1zbU29AOZsiME1iSB5SxxYzRUkQ@mail.gmail.com>
References: <CAF-nxa_aZK4fHWONXEokVdp1zbU29AOZsiME1iSB5SxxYzRUkQ@mail.gmail.com>
Message-ID: <CAAg5f2S1=QBTEVzdqEe+M1W1BP1O4Sw9o3T3Yv+q2pwtKaqVew@mail.gmail.com>

separate repo, not sure
separate WAR file, I think at some point I want to have a bunch of
different WAR files:
* sender_API.war
* registration_API.war
* ui.war
core.jar (EJB w/ the messaging, as core)

but, that's a bit in the future... we have some Swarm related JIRAs for
that

On Thu, Feb 2, 2017 at 1:31 PM, Leonardo Rossetti <lrossett at redhat.com>
wrote:

> Hello,
>
> Currently we have the UPS admin UI embedded into
> aerogear-unifiedpush-server project/repository.
>
> Could the admin-ui be a separated project (repository) with its own war
> file?
>
> While it may increase release process complexity (a new project
> dependency), I think it brings some benefits to the table, such as having a
> development cycle of this own, easier to write automated tests and easier
> to attract contributors from the javascript community (since we would be
> using common javascript tools to build it).
>
> WDYT?
>
> --
> Leonardo Rossetti
> lrossett at redhat.com
> +55 11 99703 0621 <+55%2011%2099703-0621>
>
> _______________________________________________
> 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/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170202/a95f442f/attachment.html 

From lholmqui at redhat.com  Thu Feb  2 08:50:48 2017
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 2 Feb 2017 08:50:48 -0500
Subject: [aerogear-dev] ups admin ui
In-Reply-To: <CAAg5f2S1=QBTEVzdqEe+M1W1BP1O4Sw9o3T3Yv+q2pwtKaqVew@mail.gmail.com>
References: <CAF-nxa_aZK4fHWONXEokVdp1zbU29AOZsiME1iSB5SxxYzRUkQ@mail.gmail.com>
	<CAAg5f2S1=QBTEVzdqEe+M1W1BP1O4Sw9o3T3Yv+q2pwtKaqVew@mail.gmail.com>
Message-ID: <CALD3Fd1yuhSXFWHoJVEJ3mK_T3nAjnFN8HWqb6YCK4xC0bTMyA@mail.gmail.com>

I believe the UI was in its own repo during the first iteration(when it was
ember :))


If we want to attract contributors from the JS community,  then making it a
WAR is not really a great idea,


On Thu, Feb 2, 2017 at 8:01 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> separate repo, not sure
> separate WAR file, I think at some point I want to have a bunch of
> different WAR files:
> * sender_API.war
> * registration_API.war
> * ui.war
> core.jar (EJB w/ the messaging, as core)
>
> but, that's a bit in the future... we have some Swarm related JIRAs for
> that
>
> On Thu, Feb 2, 2017 at 1:31 PM, Leonardo Rossetti <lrossett at redhat.com>
> wrote:
>
>> Hello,
>>
>> Currently we have the UPS admin UI embedded into
>> aerogear-unifiedpush-server project/repository.
>>
>> Could the admin-ui be a separated project (repository) with its own war
>> file?
>>
>> While it may increase release process complexity (a new project
>> dependency), I think it brings some benefits to the table, such as having a
>> development cycle of this own, easier to write automated tests and easier
>> to attract contributors from the javascript community (since we would be
>> using common javascript tools to build it).
>>
>> WDYT?
>>
>> --
>> Leonardo Rossetti
>> lrossett at redhat.com
>> +55 11 99703 0621 <+55%2011%2099703-0621>
>>
>> _______________________________________________
>> 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/
> 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/20170202/eee7541f/attachment-0001.html 

From matzew at apache.org  Thu Feb  2 09:04:40 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 2 Feb 2017 15:04:40 +0100
Subject: [aerogear-dev] ups admin ui
In-Reply-To: <CALD3Fd1yuhSXFWHoJVEJ3mK_T3nAjnFN8HWqb6YCK4xC0bTMyA@mail.gmail.com>
References: <CAF-nxa_aZK4fHWONXEokVdp1zbU29AOZsiME1iSB5SxxYzRUkQ@mail.gmail.com>
	<CAAg5f2S1=QBTEVzdqEe+M1W1BP1O4Sw9o3T3Yv+q2pwtKaqVew@mail.gmail.com>
	<CALD3Fd1yuhSXFWHoJVEJ3mK_T3nAjnFN8HWqb6YCK4xC0bTMyA@mail.gmail.com>
Message-ID: <CAAg5f2Qgdi0JvU6FMgxKn2gg8ZVPQDeLGBbMhUvju3Pjb3dEmg@mail.gmail.com>

On Thu, Feb 2, 2017 at 2:50 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> I believe the UI was in its own repo during the first iteration(when it
> was ember :))
>
>
yep, and it was a PITA to integrate the pure JS files


>
> If we want to attract contributors from the JS community,  then making it
> a WAR is not really a great idea,
>

sure, but... how useful is the UI outside of the context of push? and,
bundling w/ push... perhaps we release it as NPM, and include that,
somehow, into a WAR?
I see no other option for our deployment model


>
>
> On Thu, Feb 2, 2017 at 8:01 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> separate repo, not sure
>> separate WAR file, I think at some point I want to have a bunch of
>> different WAR files:
>> * sender_API.war
>> * registration_API.war
>> * ui.war
>> core.jar (EJB w/ the messaging, as core)
>>
>> but, that's a bit in the future... we have some Swarm related JIRAs for
>> that
>>
>> On Thu, Feb 2, 2017 at 1:31 PM, Leonardo Rossetti <lrossett at redhat.com>
>> wrote:
>>
>>> Hello,
>>>
>>> Currently we have the UPS admin UI embedded into
>>> aerogear-unifiedpush-server project/repository.
>>>
>>> Could the admin-ui be a separated project (repository) with its own war
>>> file?
>>>
>>> While it may increase release process complexity (a new project
>>> dependency), I think it brings some benefits to the table, such as having a
>>> development cycle of this own, easier to write automated tests and easier
>>> to attract contributors from the javascript community (since we would be
>>> using common javascript tools to build it).
>>>
>>> WDYT?
>>>
>>> --
>>> Leonardo Rossetti
>>> lrossett at redhat.com
>>> +55 11 99703 0621 <+55%2011%2099703-0621>
>>>
>>> _______________________________________________
>>> 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/
>> 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/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170202/55477ffc/attachment.html 

From scm.blanc at gmail.com  Thu Feb  2 10:32:05 2017
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 2 Feb 2017 16:32:05 +0100
Subject: [aerogear-dev] ups admin ui
In-Reply-To: <CAAg5f2Qgdi0JvU6FMgxKn2gg8ZVPQDeLGBbMhUvju3Pjb3dEmg@mail.gmail.com>
References: <CAF-nxa_aZK4fHWONXEokVdp1zbU29AOZsiME1iSB5SxxYzRUkQ@mail.gmail.com>
	<CAAg5f2S1=QBTEVzdqEe+M1W1BP1O4Sw9o3T3Yv+q2pwtKaqVew@mail.gmail.com>
	<CALD3Fd1yuhSXFWHoJVEJ3mK_T3nAjnFN8HWqb6YCK4xC0bTMyA@mail.gmail.com>
	<CAAg5f2Qgdi0JvU6FMgxKn2gg8ZVPQDeLGBbMhUvju3Pjb3dEmg@mail.gmail.com>
Message-ID: <CAD_dpu195w9yC164zk-ebEo-AQk3QQ-GqeNxes4zC4OT2o3mwQ@mail.gmail.com>

On Thu, Feb 2, 2017 at 3:04 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Thu, Feb 2, 2017 at 2:50 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> I believe the UI was in its own repo during the first iteration(when it
>> was ember :))
>>
>>
> yep, and it was a PITA to integrate the pure JS files
>
>
>>
>> If we want to attract contributors from the JS community,  then making it
>> a WAR is not really a great idea,
>>
>
> sure, but... how useful is the UI outside of the context of push? and,
> bundling w/ push... perhaps we release it as NPM, and include that,
> somehow, into a WAR?
>
I think we already publish it as NPM module for the integration with RHMAP.


> I see no other option for our deployment model
>
>
>>
>>
>> On Thu, Feb 2, 2017 at 8:01 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> separate repo, not sure
>>> separate WAR file, I think at some point I want to have a bunch of
>>> different WAR files:
>>> * sender_API.war
>>> * registration_API.war
>>> * ui.war
>>> core.jar (EJB w/ the messaging, as core)
>>>
>>> but, that's a bit in the future... we have some Swarm related JIRAs for
>>> that
>>>
>>> On Thu, Feb 2, 2017 at 1:31 PM, Leonardo Rossetti <lrossett at redhat.com>
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> Currently we have the UPS admin UI embedded into
>>>> aerogear-unifiedpush-server project/repository.
>>>>
>>>> Could the admin-ui be a separated project (repository) with its own war
>>>> file?
>>>>
>>>> While it may increase release process complexity (a new project
>>>> dependency), I think it brings some benefits to the table, such as having a
>>>> development cycle of this own, easier to write automated tests and easier
>>>> to attract contributors from the javascript community (since we would be
>>>> using common javascript tools to build it).
>>>>
>>>> WDYT?
>>>>
>>>> --
>>>> Leonardo Rossetti
>>>> lrossett at redhat.com
>>>> +55 11 99703 0621 <+55%2011%2099703-0621>
>>>>
>>>> _______________________________________________
>>>> 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/
>>> 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/
> 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/20170202/6ad75c01/attachment.html 

From lrossett at redhat.com  Thu Feb  2 10:58:34 2017
From: lrossett at redhat.com (Leonardo Rossetti)
Date: Thu, 2 Feb 2017 13:58:34 -0200
Subject: [aerogear-dev] ups admin ui
In-Reply-To: <CAD_dpu195w9yC164zk-ebEo-AQk3QQ-GqeNxes4zC4OT2o3mwQ@mail.gmail.com>
References: <CAF-nxa_aZK4fHWONXEokVdp1zbU29AOZsiME1iSB5SxxYzRUkQ@mail.gmail.com>
	<CAAg5f2S1=QBTEVzdqEe+M1W1BP1O4Sw9o3T3Yv+q2pwtKaqVew@mail.gmail.com>
	<CALD3Fd1yuhSXFWHoJVEJ3mK_T3nAjnFN8HWqb6YCK4xC0bTMyA@mail.gmail.com>
	<CAAg5f2Qgdi0JvU6FMgxKn2gg8ZVPQDeLGBbMhUvju3Pjb3dEmg@mail.gmail.com>
	<CAD_dpu195w9yC164zk-ebEo-AQk3QQ-GqeNxes4zC4OT2o3mwQ@mail.gmail.com>
Message-ID: <CAF-nxa8YSFwpypmA13TC94Kbc2cPOdv5bCxCXPXEGiBYVNjkLw@mail.gmail.com>

WAR/JAR file would be for UPS deployment/build only, the repository itself
would only contain frontend related files (being published in NPM as well).

Did a quick search on NPM and found this package[1], is this the one?

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

On Thu, Feb 2, 2017 at 1:32 PM, Sebastien Blanc <scm.blanc at gmail.com> wrote:

>
>
> On Thu, Feb 2, 2017 at 3:04 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Thu, Feb 2, 2017 at 2:50 PM, Luke Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>> I believe the UI was in its own repo during the first iteration(when it
>>> was ember :))
>>>
>>>
>> yep, and it was a PITA to integrate the pure JS files
>>
>>
>>>
>>> If we want to attract contributors from the JS community,  then making
>>> it a WAR is not really a great idea,
>>>
>>
>> sure, but... how useful is the UI outside of the context of push? and,
>> bundling w/ push... perhaps we release it as NPM, and include that,
>> somehow, into a WAR?
>>
> I think we already publish it as NPM module for the integration with
> RHMAP.
>
>> I see no other option for our deployment model
>>
>>
>>>
>>>
>>> On Thu, Feb 2, 2017 at 8:01 AM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> separate repo, not sure
>>>> separate WAR file, I think at some point I want to have a bunch of
>>>> different WAR files:
>>>> * sender_API.war
>>>> * registration_API.war
>>>> * ui.war
>>>> core.jar (EJB w/ the messaging, as core)
>>>>
>>>> but, that's a bit in the future... we have some Swarm related JIRAs for
>>>> that
>>>>
>>>> On Thu, Feb 2, 2017 at 1:31 PM, Leonardo Rossetti <lrossett at redhat.com>
>>>> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> Currently we have the UPS admin UI embedded into
>>>>> aerogear-unifiedpush-server project/repository.
>>>>>
>>>>> Could the admin-ui be a separated project (repository) with its own
>>>>> war file?
>>>>>
>>>>> While it may increase release process complexity (a new project
>>>>> dependency), I think it brings some benefits to the table, such as having a
>>>>> development cycle of this own, easier to write automated tests and easier
>>>>> to attract contributors from the javascript community (since we would be
>>>>> using common javascript tools to build it).
>>>>>
>>>>> WDYT?
>>>>>
>>>>> --
>>>>> Leonardo Rossetti
>>>>> lrossett at redhat.com
>>>>> +55 11 99703 0621 <+55%2011%2099703-0621>
>>>>>
>>>>> _______________________________________________
>>>>> 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/
>>>> 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/
>> 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
>



-- 
Leonardo Rossetti
lrossett at redhat.com
+55 11 99703 0621
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170202/ccdd40ac/attachment-0001.html 

From scm.blanc at gmail.com  Thu Feb  2 11:06:14 2017
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Thu, 2 Feb 2017 17:06:14 +0100
Subject: [aerogear-dev] ups admin ui
In-Reply-To: <CAF-nxa8YSFwpypmA13TC94Kbc2cPOdv5bCxCXPXEGiBYVNjkLw@mail.gmail.com>
References: <CAF-nxa_aZK4fHWONXEokVdp1zbU29AOZsiME1iSB5SxxYzRUkQ@mail.gmail.com>
	<CAAg5f2S1=QBTEVzdqEe+M1W1BP1O4Sw9o3T3Yv+q2pwtKaqVew@mail.gmail.com>
	<CALD3Fd1yuhSXFWHoJVEJ3mK_T3nAjnFN8HWqb6YCK4xC0bTMyA@mail.gmail.com>
	<CAAg5f2Qgdi0JvU6FMgxKn2gg8ZVPQDeLGBbMhUvju3Pjb3dEmg@mail.gmail.com>
	<CAD_dpu195w9yC164zk-ebEo-AQk3QQ-GqeNxes4zC4OT2o3mwQ@mail.gmail.com>
	<CAF-nxa8YSFwpypmA13TC94Kbc2cPOdv5bCxCXPXEGiBYVNjkLw@mail.gmail.com>
Message-ID: <CAD_dpu1LUQGXsdeOG2NgFjU1EBWZ1xMaXsk-BWoNssuQ=jCuJw@mail.gmail.com>

On Thu, Feb 2, 2017 at 4:58 PM, Leonardo Rossetti <lrossett at redhat.com>
wrote:

> WAR/JAR file would be for UPS deployment/build only, the repository itself
> would only contain frontend related files (being published in NPM as well).
>
> Did a quick search on NPM and found this package[1], is this the one?
>
> [1] - https://www.npmjs.com/package/unifiedpush-admin-client
>
No I think it's this one https://www.npmjs.com/package/ups-admin-ui


>
> On Thu, Feb 2, 2017 at 1:32 PM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>>
>>
>> On Thu, Feb 2, 2017 at 3:04 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>>
>>>
>>> On Thu, Feb 2, 2017 at 2:50 PM, Luke Holmquist <lholmqui at redhat.com>
>>> wrote:
>>>
>>>> I believe the UI was in its own repo during the first iteration(when it
>>>> was ember :))
>>>>
>>>>
>>> yep, and it was a PITA to integrate the pure JS files
>>>
>>>
>>>>
>>>> If we want to attract contributors from the JS community,  then making
>>>> it a WAR is not really a great idea,
>>>>
>>>
>>> sure, but... how useful is the UI outside of the context of push? and,
>>> bundling w/ push... perhaps we release it as NPM, and include that,
>>> somehow, into a WAR?
>>>
>> I think we already publish it as NPM module for the integration with
>> RHMAP.
>>
>>> I see no other option for our deployment model
>>>
>>>
>>>>
>>>>
>>>> On Thu, Feb 2, 2017 at 8:01 AM, Matthias Wessendorf <matzew at apache.org>
>>>> wrote:
>>>>
>>>>> separate repo, not sure
>>>>> separate WAR file, I think at some point I want to have a bunch of
>>>>> different WAR files:
>>>>> * sender_API.war
>>>>> * registration_API.war
>>>>> * ui.war
>>>>> core.jar (EJB w/ the messaging, as core)
>>>>>
>>>>> but, that's a bit in the future... we have some Swarm related JIRAs
>>>>> for that
>>>>>
>>>>> On Thu, Feb 2, 2017 at 1:31 PM, Leonardo Rossetti <lrossett at redhat.com
>>>>> > wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Currently we have the UPS admin UI embedded into
>>>>>> aerogear-unifiedpush-server project/repository.
>>>>>>
>>>>>> Could the admin-ui be a separated project (repository) with its own
>>>>>> war file?
>>>>>>
>>>>>> While it may increase release process complexity (a new project
>>>>>> dependency), I think it brings some benefits to the table, such as having a
>>>>>> development cycle of this own, easier to write automated tests and easier
>>>>>> to attract contributors from the javascript community (since we would be
>>>>>> using common javascript tools to build it).
>>>>>>
>>>>>> WDYT?
>>>>>>
>>>>>> --
>>>>>> Leonardo Rossetti
>>>>>> lrossett at redhat.com
>>>>>> +55 11 99703 0621 <+55%2011%2099703-0621>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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/
>>>>> 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/
>>> 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
>>
>
>
>
> --
> Leonardo Rossetti
> lrossett at redhat.com
> +55 11 99703 0621 <+55%2011%2099703-0621>
>
> _______________________________________________
> 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/20170202/422e138c/attachment.html 

From lholmqui at redhat.com  Thu Feb  2 11:11:29 2017
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 2 Feb 2017 11:11:29 -0500
Subject: [aerogear-dev] ups admin ui
In-Reply-To: <CAF-nxa8YSFwpypmA13TC94Kbc2cPOdv5bCxCXPXEGiBYVNjkLw@mail.gmail.com>
References: <CAF-nxa_aZK4fHWONXEokVdp1zbU29AOZsiME1iSB5SxxYzRUkQ@mail.gmail.com>
	<CAAg5f2S1=QBTEVzdqEe+M1W1BP1O4Sw9o3T3Yv+q2pwtKaqVew@mail.gmail.com>
	<CALD3Fd1yuhSXFWHoJVEJ3mK_T3nAjnFN8HWqb6YCK4xC0bTMyA@mail.gmail.com>
	<CAAg5f2Qgdi0JvU6FMgxKn2gg8ZVPQDeLGBbMhUvju3Pjb3dEmg@mail.gmail.com>
	<CAD_dpu195w9yC164zk-ebEo-AQk3QQ-GqeNxes4zC4OT2o3mwQ@mail.gmail.com>
	<CAF-nxa8YSFwpypmA13TC94Kbc2cPOdv5bCxCXPXEGiBYVNjkLw@mail.gmail.com>
Message-ID: <CALD3Fd3EZ=5iAdvxsjkm374DytcXC6iUS6-PC4OBX2iOiaF+5g@mail.gmail.com>

On Thu, Feb 2, 2017 at 10:58 AM, Leonardo Rossetti <lrossett at redhat.com>
wrote:

> WAR/JAR file would be for UPS deployment/build only, the repository itself
> would only contain frontend related files (being published in NPM as well).
>
> Did a quick search on NPM and found this package[1], is this the one?
>
> [1] - https://www.npmjs.com/package/unifiedpush-admin-client
>
that's not the one.   i do believe that is being used though in your new
node-test-suite thing

>
> On Thu, Feb 2, 2017 at 1:32 PM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>>
>>
>> On Thu, Feb 2, 2017 at 3:04 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>>
>>>
>>> On Thu, Feb 2, 2017 at 2:50 PM, Luke Holmquist <lholmqui at redhat.com>
>>> wrote:
>>>
>>>> I believe the UI was in its own repo during the first iteration(when it
>>>> was ember :))
>>>>
>>>>
>>> yep, and it was a PITA to integrate the pure JS files
>>>
>>>
>>>>
>>>> If we want to attract contributors from the JS community,  then making
>>>> it a WAR is not really a great idea,
>>>>
>>>
>>> sure, but... how useful is the UI outside of the context of push? and,
>>> bundling w/ push... perhaps we release it as NPM, and include that,
>>> somehow, into a WAR?
>>>
>> I think we already publish it as NPM module for the integration with
>> RHMAP.
>>
>>> I see no other option for our deployment model
>>>
>>>
>>>>
>>>>
>>>> On Thu, Feb 2, 2017 at 8:01 AM, Matthias Wessendorf <matzew at apache.org>
>>>> wrote:
>>>>
>>>>> separate repo, not sure
>>>>> separate WAR file, I think at some point I want to have a bunch of
>>>>> different WAR files:
>>>>> * sender_API.war
>>>>> * registration_API.war
>>>>> * ui.war
>>>>> core.jar (EJB w/ the messaging, as core)
>>>>>
>>>>> but, that's a bit in the future... we have some Swarm related JIRAs
>>>>> for that
>>>>>
>>>>> On Thu, Feb 2, 2017 at 1:31 PM, Leonardo Rossetti <lrossett at redhat.com
>>>>> > wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Currently we have the UPS admin UI embedded into
>>>>>> aerogear-unifiedpush-server project/repository.
>>>>>>
>>>>>> Could the admin-ui be a separated project (repository) with its own
>>>>>> war file?
>>>>>>
>>>>>> While it may increase release process complexity (a new project
>>>>>> dependency), I think it brings some benefits to the table, such as having a
>>>>>> development cycle of this own, easier to write automated tests and easier
>>>>>> to attract contributors from the javascript community (since we would be
>>>>>> using common javascript tools to build it).
>>>>>>
>>>>>> WDYT?
>>>>>>
>>>>>> --
>>>>>> Leonardo Rossetti
>>>>>> lrossett at redhat.com
>>>>>> +55 11 99703 0621 <+55%2011%2099703-0621>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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/
>>>>> 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/
>>> 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
>>
>
>
>
> --
> Leonardo Rossetti
> lrossett at redhat.com
> +55 11 99703 0621 <+55%2011%2099703-0621>
>
> _______________________________________________
> 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/20170202/bf7587e1/attachment-0001.html 

From matzew at apache.org  Sat Feb 18 09:09:44 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Sat, 18 Feb 2017 15:09:44 +0100
Subject: [aerogear-dev] Push - Batch processing endpoint ?
Message-ID: <CAAg5f2Sv=UU-a5-RZ6zR1q-W+8ArT3R5kre7aN8ALQyZ9VCiqg@mail.gmail.com>

Hi,

how do people feel about an batch processing endpoint:
https://github.com/aerogear/aerogear-unifiedpush-server/pull/794

Use-case:
If you have a list of different users (via different alias), and want to
send them a personalized message (e.g. "Hello $alias, how are things?"),
CURRENTLY you'd have to iterate through that list and send a push request
for _each_ alias/message pair. Which results in lot's of overhead, and
lot's of http requests;

Now, using this new batch endpoint, allows you do iterate through the list,
create the actual message, put it to a collection, and after the iteration,
you send one HTTP request, containing the message collection.

This results in ONE http request, which it may contain 100's of different
messages, for the given Push-Application, instead of 100's of HTTP requests.

Any thoughts ?

-Matthias

-- 
Matthias Wessendorf

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

From matzew at apache.org  Sat Feb 18 13:58:24 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Sat, 18 Feb 2017 19:58:24 +0100
Subject: [aerogear-dev] Push - Batch processing endpoint ?
In-Reply-To: <CAAg5f2Sv=UU-a5-RZ6zR1q-W+8ArT3R5kre7aN8ALQyZ9VCiqg@mail.gmail.com>
References: <CAAg5f2Sv=UU-a5-RZ6zR1q-W+8ArT3R5kre7aN8ALQyZ9VCiqg@mail.gmail.com>
Message-ID: <CAAg5f2TKii7MPUeZvMQ+xov5mt_6NmWHkEu34Gg__tQppgecTw@mail.gmail.com>

the java client update looks like:
https://github.com/aerogear/aerogear-unifiedpush-java-client/pull/82

Was not hard, some java8 fu, and just appending, internally, the "batch"
part of the URL

-M

On Sat, Feb 18, 2017 at 3:09 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> how do people feel about an batch processing endpoint:
> https://github.com/aerogear/aerogear-unifiedpush-server/pull/794
>
> Use-case:
> If you have a list of different users (via different alias), and want to
> send them a personalized message (e.g. "Hello $alias, how are things?"),
> CURRENTLY you'd have to iterate through that list and send a push request
> for _each_ alias/message pair. Which results in lot's of overhead, and
> lot's of http requests;
>
> Now, using this new batch endpoint, allows you do iterate through the
> list, create the actual message, put it to a collection, and after the
> iteration, you send one HTTP request, containing the message collection.
>
> This results in ONE http request, which it may contain 100's of different
> messages, for the given Push-Application, instead of 100's of HTTP requests.
>
> Any thoughts ?
>
> -Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

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

From supittma at redhat.com  Sun Feb 19 12:56:26 2017
From: supittma at redhat.com (Summers Pittman)
Date: Sun, 19 Feb 2017 12:56:26 -0500
Subject: [aerogear-dev] Push - Batch processing endpoint ?
In-Reply-To: <CAAg5f2TKii7MPUeZvMQ+xov5mt_6NmWHkEu34Gg__tQppgecTw@mail.gmail.com>
References: <CAAg5f2Sv=UU-a5-RZ6zR1q-W+8ArT3R5kre7aN8ALQyZ9VCiqg@mail.gmail.com>
	<CAAg5f2TKii7MPUeZvMQ+xov5mt_6NmWHkEu34Gg__tQppgecTw@mail.gmail.com>
Message-ID: <CAEQz2CuBpHtC3wRtHWyv8mAnyb7Z-YKMUkum_wT8df6Z8kObdw@mail.gmail.com>

Oooo That looks cool, I've starred it to take a closer look.

On Sat, Feb 18, 2017 at 1:58 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> the java client update looks like:
> https://github.com/aerogear/aerogear-unifiedpush-java-client/pull/82
>
> Was not hard, some java8 fu, and just appending, internally, the "batch"
> part of the URL
>
> -M
>
> On Sat, Feb 18, 2017 at 3:09 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> how do people feel about an batch processing endpoint:
>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/794
>>
>> Use-case:
>> If you have a list of different users (via different alias), and want to
>> send them a personalized message (e.g. "Hello $alias, how are things?"),
>> CURRENTLY you'd have to iterate through that list and send a push request
>> for _each_ alias/message pair. Which results in lot's of overhead, and
>> lot's of http requests;
>>
>> Now, using this new batch endpoint, allows you do iterate through the
>> list, create the actual message, put it to a collection, and after the
>> iteration, you send one HTTP request, containing the message collection.
>>
>> This results in ONE http request, which it may contain 100's of different
>> messages, for the given Push-Application, instead of 100's of HTTP requests.
>>
>> Any thoughts ?
>>
>> -Matthias
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170219/39f12e0a/attachment.html 

From jgallaso at redhat.com  Mon Feb 20 03:02:09 2017
From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo)
Date: Mon, 20 Feb 2017 09:02:09 +0100
Subject: [aerogear-dev] Push - Batch processing endpoint ?
In-Reply-To: <CAEQz2CuBpHtC3wRtHWyv8mAnyb7Z-YKMUkum_wT8df6Z8kObdw@mail.gmail.com>
References: <CAAg5f2Sv=UU-a5-RZ6zR1q-W+8ArT3R5kre7aN8ALQyZ9VCiqg@mail.gmail.com>
	<CAAg5f2TKii7MPUeZvMQ+xov5mt_6NmWHkEu34Gg__tQppgecTw@mail.gmail.com>
	<CAEQz2CuBpHtC3wRtHWyv8mAnyb7Z-YKMUkum_wT8df6Z8kObdw@mail.gmail.com>
Message-ID: <CAGsbZmECy1VRLK63aELKAryid3Tqy+WHdMW8tSmnm2YhiFQpvQ@mail.gmail.com>

?Looks like a very nice feature. I wonder if it will cause very large HTTP
request payloads and how problematic this could be? My browser is sometimes
slow when loading some heavy website so sending a huge batch might not be
so much productive after all. What do you thing?

Disclaimer: this is not a criticism but a innocent question.

Cheers,

On 19 February 2017 at 18:56, Summers Pittman <supittma at redhat.com> wrote:

> Oooo That looks cool, I've starred it to take a closer look.
>
> On Sat, Feb 18, 2017 at 1:58 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> the java client update looks like:
>> https://github.com/aerogear/aerogear-unifiedpush-java-client/pull/82
>>
>> Was not hard, some java8 fu, and just appending, internally, the "batch"
>> part of the URL
>>
>> -M
>>
>> On Sat, Feb 18, 2017 at 3:09 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> how do people feel about an batch processing endpoint:
>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/794
>>>
>>> Use-case:
>>> If you have a list of different users (via different alias), and want to
>>> send them a personalized message (e.g. "Hello $alias, how are things?"),
>>> CURRENTLY you'd have to iterate through that list and send a push request
>>> for _each_ alias/message pair. Which results in lot's of overhead, and
>>> lot's of http requests;
>>>
>>> Now, using this new batch endpoint, allows you do iterate through the
>>> list, create the actual message, put it to a collection, and after the
>>> iteration, you send one HTTP request, containing the message collection.
>>>
>>> This results in ONE http request, which it may contain 100's of
>>> different messages, for the given Push-Application, instead of 100's of
>>> HTTP requests.
>>>
>>> Any thoughts ?
>>>
>>> -Matthias
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
*Jose Miguel Gallas Olmedo*
Associate QE at Mobile Team, *Red Hat*
<https://www.redhat.com/en/technologies/mobile/application-platform>
+34 618 488 633
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170220/8272e1fa/attachment-0001.html 

From matzew at apache.org  Mon Feb 20 04:33:11 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 20 Feb 2017 10:33:11 +0100
Subject: [aerogear-dev] Push - Batch processing endpoint ?
In-Reply-To: <CAGsbZmECy1VRLK63aELKAryid3Tqy+WHdMW8tSmnm2YhiFQpvQ@mail.gmail.com>
References: <CAAg5f2Sv=UU-a5-RZ6zR1q-W+8ArT3R5kre7aN8ALQyZ9VCiqg@mail.gmail.com>
	<CAAg5f2TKii7MPUeZvMQ+xov5mt_6NmWHkEu34Gg__tQppgecTw@mail.gmail.com>
	<CAEQz2CuBpHtC3wRtHWyv8mAnyb7Z-YKMUkum_wT8df6Z8kObdw@mail.gmail.com>
	<CAGsbZmECy1VRLK63aELKAryid3Tqy+WHdMW8tSmnm2YhiFQpvQ@mail.gmail.com>
Message-ID: <CAAg5f2RCYop6PBPB0gXsH+hYX9Vzn_QPVnpLt=V9QLfvnY=KDw@mail.gmail.com>

Submitting is fully handled asyn. e.g. it took me 350ms to submit 5k of
push messages.
than client returns;

The messaging sub-system of WildFly/EAP than processes those, in batches
(e.g. per push network etc)

So, if one sends 100k messages in one batch, the same would be very likely
sent via individual requests.
but here we have 1 request, instead of 100k, which also has lot's of
problems in terms of costs/overhead

Mainly the internal message broker is decoupled from the web-workers,
hence, once uploaded, the processing on the messaging component.

That said, I also think that our Google Summer of Code project
(Kafka/HBase) will greatly contribute to a much faster system, being able
to handle crazy loads, which is currently already not really possible

PS: I've added a comment to the server PR,

On Mon, Feb 20, 2017 at 9:02 AM, Jose Miguel Gallas Olmedo <
jgallaso at redhat.com> wrote:

> ?Looks like a very nice feature. I wonder if it will cause very large HTTP
> request payloads and how problematic this could be? My browser is sometimes
> slow when loading some heavy website so sending a huge batch might not be
> so much productive after all. What do you thing?
>
> Disclaimer: this is not a criticism but a innocent question.
>
> Cheers,
>
> On 19 February 2017 at 18:56, Summers Pittman <supittma at redhat.com> wrote:
>
>> Oooo That looks cool, I've starred it to take a closer look.
>>
>> On Sat, Feb 18, 2017 at 1:58 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> the java client update looks like:
>>> https://github.com/aerogear/aerogear-unifiedpush-java-client/pull/82
>>>
>>> Was not hard, some java8 fu, and just appending, internally, the "batch"
>>> part of the URL
>>>
>>> -M
>>>
>>> On Sat, Feb 18, 2017 at 3:09 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> how do people feel about an batch processing endpoint:
>>>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/794
>>>>
>>>> Use-case:
>>>> If you have a list of different users (via different alias), and want
>>>> to send them a personalized message (e.g. "Hello $alias, how are things?"),
>>>> CURRENTLY you'd have to iterate through that list and send a push request
>>>> for _each_ alias/message pair. Which results in lot's of overhead, and
>>>> lot's of http requests;
>>>>
>>>> Now, using this new batch endpoint, allows you do iterate through the
>>>> list, create the actual message, put it to a collection, and after the
>>>> iteration, you send one HTTP request, containing the message collection.
>>>>
>>>> This results in ONE http request, which it may contain 100's of
>>>> different messages, for the given Push-Application, instead of 100's of
>>>> HTTP requests.
>>>>
>>>> Any thoughts ?
>>>>
>>>> -Matthias
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> *Jose Miguel Gallas Olmedo*
> Associate QE at Mobile Team, *Red Hat*
> <https://www.redhat.com/en/technologies/mobile/application-platform>
> +34 618 488 633 <+34%20618%2048%2086%2033>
>
> _______________________________________________
> 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/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170220/665cff4d/attachment.html