Good morning, first nice screencast Sebi and even knowing this is just a
PoC I have some considerations:
1. What would be the use case scenario to justify a separated server
instead of just a module on AGPUSH?
2. How do you plan to prevent people from faking their location?
3. Do we have a privacy policy to make the developer real aware about
what's being collected?
4. Will collecting geo location be opt in or default?
5. Why is necessary to store current user's position?
Couldn't admin
specify a range and check how many devices are active on that region?
Into this way you don't need to store their positions. I'm not the Geo
specialist here but the idea is:
1. Admin specify the range when a push message must be sent. For
example: Whole Florida
2. Client opt in and sent her its position to the server
3. Server compares and sent the push message
I'm very concerned about privacy here, I'm not against the
solution, but Geo location is like to open a Pandora box.
We might be careful about unintentional disclosure of geolocation information,
because it carries physical risks to the client (theft, to stalking, kidnapping
and domestic violence — I'm not exaggerating).
Again, I know this is a proof of concept, but sooner we have it in mind, the
better.
> _______________________________________________
On 2014-12-10, Sebastien Blanc wrote:
> Hi all,
>
> I have been working on a POC around geolocation. Like we discussed in
> another thread, we decided not to have a "deep" integration with the Push
> server but instead a separate component / microservice. Well the POC is
> more a miniservice ;)
>
> So, the idea is to have a server to which devices can register by providing
> their positions. On the other side, the server provide an endpoint to make
> spatial queries, like give me all the installations within a radius of 10
> km around this lat/ltg.
>
> Thanks to Forge, I created/scaffolded a really simple server providing the
> registration endpoint and the search endpoint.
>
> I tried to make a decent readme that will give you more details :
>
> https://github.com/sebastienblanc/unified-geo-server
>
> And as usual, I made a little screencast showing all that in action ;)
>
> https://www.youtube.com/watch?v=R-qdLJh4EWQ
>
> Please remember this is a POC, so the security is almost inexistant, the
> console is awful ;)
>
> What about the Client SDKs ?
>
> If we reach some kind of consensus arounf the concept of Unfied Geo Server
> we can start building the Client SDKs / POCs , they will be quite simple :
> retrieve geolocation and register to the geo endpoint.
>
> Sebi
> aerogear-dev mailing list
> aerogear-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
PGP: 0x84DC9914
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev