<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 10, 2014 at 4:46 PM, Andres Galante <span dir="ltr"><<a href="mailto:agalante@redhat.com" target="_blank">agalante@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Nice work Sebastien!<br>
If you I can help with app or console design, please let me know.<br></blockquote><div>Thanks ! A good strategy would probably to follow the Push Server and LiveOak (Angular/patternfly) model.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div><br>
----- Original Message -----<br>
From: "Sebastien Blanc" <<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>><br>
To: "AeroGear Developer Mailing List" <<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a>><br>
Sent: Wednesday, December 10, 2014 12:28:43 PM<br>
Subject: Re: [aerogear-dev] [POC] Unified Geo Server<br>
<br>
<br>
<br>
On Wed, Dec 10, 2014 at 4:23 PM, Erik Jan de Wit < <a href="mailto:edewit@redhat.com" target="_blank">edewit@redhat.com</a> > wrote:<br>
<br>
<br>
Really nice, looks great already, one question how do I use the data<br>
from the geo search to send push notifications?<br>
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.<br>
It tried to described that here : <a href="https://github.com/sebastienblanc/unified-geo-server#integration-with-push" target="_blank">https://github.com/sebastienblanc/unified-geo-server#integration-with-push</a><br>
<br>
One idea for the alias, is to use the Keycloak (or whatever auth system) username as alias to have it somehow "unified"<br>
<br>
<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br></div></div>