[aerogear-dev] [POC] Unified Geo Server

[Sebastien Blanc]

On Wed, Dec 10, 2014 at 4:46 PM, Andres Galante <agalante at 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 at gmail.com>
> To: "AeroGear Developer Mailing List" <aerogear-dev at 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 at 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 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/20141210/a9909ddb/attachment-0001.html