<div dir="ltr">Thanks for the screencast!</div><div class="gmail_extra"><br><div class="gmail_quote">On 10 December 2014 at 21:23, Sébastien Blanc <span dir="ltr"><<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
Envoyé de mon iPhone<br>
<br>
> Le 10 déc. 2014 à 20:55, Corinne Krych <<a href="mailto:corinnekrych@gmail.com">corinnekrych@gmail.com</a>> a écrit :<br>
<span class="">><br>
> Nice POC indeed, it makes things more concrete.<br>
><br>
> 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.<br>
> With the same idea some of the admin console for creating app could be mutualised.<br>
</span>Make totally sense and I have also been thinking about that.<br>
My first thoughts would be something's around fabric8/fuse and using amq.<br>
One concrete example that I will try to add to the POC is sending a message on a amq channel when a device registers. Other apps could consume this queue. That might be a start.<br>
<div class="HOEnZb"><div class="h5">><br>
> This is more a ‘for the future’ improvement and does not interfere with your POC.<br>
><br>
> ++<br>
> Corinne<br>
><br>
>> On 10 Dec 2014, at 17:12, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>> wrote:<br>
>><br>
>><br>
>><br>
>> On Wed, Dec 10, 2014 at 4:46 PM, Andres Galante <<a href="mailto:agalante@redhat.com">agalante@redhat.com</a>> wrote:<br>
>> Nice work Sebastien!<br>
>> If you I can help with app or console design, please let me know.<br>
>> Thanks ! A good strategy would probably to follow the Push Server and LiveOak (Angular/patternfly) model.<br>
>><br>
>> ----- Original Message -----<br>
>> From: "Sebastien Blanc" <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>><br>
>> To: "AeroGear Developer Mailing List" <<a href="mailto:aerogear-dev@lists.jboss.org">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">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">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">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">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>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org">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">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>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">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></div></div></blockquote></div><br></div>