[aerogear-dev] [POC] Unified Geo Server

Matthias Wessendorf matzew at apache.org
Thu Dec 11 02:53:06 EST 2014


Nice POC, Sebi! and great screencast!

On Wed, Dec 10, 2014 at 8:55 PM, Corinne Krych <corinnekrych at gmail.com>
wrote:

> 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 have analytics in mind (e.g. leveraging RHQ metrics, as a possible option)


> 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.
>

This overall aggregator would be an MBaaS, like FH or LiveOak. That's
really not what we need to create here

-Matthias



> 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 at gmail.com> wrote:
> >
> >
> >
> > 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
> >
> > _______________________________________________
> > 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/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141211/50f7075a/attachment.html 


More information about the aerogear-dev mailing list