2:04 p.m.
+1
We are thinking of this kind of scenarios for the next step on the console UI. The way we
have the navigation now it is not flexible enough. Hopefully I'll have updates on
console UX to share with you soon :)
----- Original Message -----
From: "Corinne Krych" <corinnekrych(a)gmail.com>
To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org>
Sent: Wednesday, December 10, 2014 4:55:56 PM
Subject: Re: [aerogear-dev] [POC] Unified Geo Server
Nice POC indeed, it makes things more concrete.
Looking at the the similar process for UGS and UPS and thinking we might need similar
mini/micro services, I think eventually we will benefit having a form of aggregator where
you say: create an app for UPS with plugin UGS, under the cover, 2 app ids are created and
unified with one appId + a map of corresponding app ids.
With the same idea some of the admin console for creating app could be mutualised.
This is more a ‘for the future’ improvement and does not interfere with your POC.
++
Corinne
On 10 Dec 2014, at 17:12, Sebastien Blanc <scm.blanc(a)gmail.com>
wrote:
On Wed, Dec 10, 2014 at 4:46 PM, Andres Galante <agalante(a)redhat.com> wrote:
Nice work Sebastien!
If you I can help with app or console design, please let me know.
Thanks ! A good strategy would probably to follow the Push Server and LiveOak
(Angular/patternfly) model.
----- Original Message -----
From: "Sebastien Blanc" <scm.blanc(a)gmail.com>
To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org>
Sent: Wednesday, December 10, 2014 12:28:43 PM
Subject: Re: [aerogear-dev] [POC] Unified Geo Server
On Wed, Dec 10, 2014 at 4:23 PM, Erik Jan de Wit < edewit(a)redhat.com > wrote:
Really nice, looks great already, one question how do I use the data
from the geo search to send push notifications?
When the device registers to the geo server, it also provides an "alias". The
idea is that the developer has to use the same "alias" when registering to the
UPS, then it's up to the backend app to retrieve the aliases for the geoserver and use
these as criteria when sending a push notif to UPS.
It tried to described that here :
https://github.com/sebastienblanc/unified-geo-server#integration-with-push
One idea for the alias, is to use the Keycloak (or whatever auth system) username as
alias to have it somehow "unified"
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev