OT: question about real-time location-sensitive message broadcasts

[Stephen Partington]

Google now works on this similar methodology. i wonder how much of their
transport you could learn from?


On Wed, Jul 30, 2014 at 10:30 AM, Ed <plug at 0x1b.com> wrote:

> On Wed, Jul 30, 2014 at 9:25 AM, David Schwartz
> <newsletters at thetoolwiz.com> wrote:
> > Thanks, but what I'm really looking for is insights around the data
> > transport, although I do understand what you're saying about using a
> > third-party service like Twitter. Perhaps there are services already
> > designed for such stuff?
>
> This sounds like Google Wave - which has migrated to an Apache
> Incubation Project - Wave in a Box (WiaB)
> https://en.wikipedia.org/wiki/Apache_Wave
> https://incubator.apache.org/wave/
>
> still a WIP but the server side might cover your needs.
>
>
> >
> > (BTW, this has absolutely NOTHING to do with things like free food
> offers.
> > It's just an example I came up with that has similar dynamics to the
> actual
> > problem I'm addressing.)
> >
> >> So we could broadcast each announcement message to everybody (all
> current
> >> listeners) in real-time (like what Twitter would do) and let the
> client-side
> >> filter out the irrelevant messages (around 99.99%).
> >>
> >> Or we could reduce that bandwidth by having clients update the server
> >> periodically (eg., every 5 minutes) with their location, then for each
> >> announcement, a server would locate clients within a reasonable radius
> based
> >> on their last reported position and only notify them directly through a
> push
> >> notification of some sort; the clients would still do some filtering,
> but
> >> this would reduce incoming traffic considerably.
> >>
> >> I'm not sure which is worse: a server updating a huge number of clients
> in
> >> near real-time, or a huge number of clients updating the server with
> their
> >> geographical location every 5 minutes or so.
> >>
> >> Or, an alternative is for the clients to poll the server every 15-30
> >> seconds, but this seems even worse in terms of traffic. (Althought this
> >> approach is probably ok if we used an existing platform like Twitter.)
> >
> >
> > Are these sorts of concerns things that anybody even worries about these
> > days? (Ie., that bandwidth is becoming so cheap and plentiful that it's
> just
> > not much of a concern down the road.)
> >
> > -David
> >
> >
> >
> > On Jul 30, 2014, at 5:51 AM, Stephen Partington <cryptworks at gmail.com>
> > wrote:
> >
> > Well you will need to tag your content for preferences. On account
> creation
> > you do a questionnaire. So that is now in a database. The you tie your
> app
> > into the location services. That would ping back and everything in
> "range"
> > would be tagged and made available in the apps offer screen. With a
> single
> > notification of offers in your area. I would not suggest using another
> > service as your transport as that can get your Data banned.
> >
> >
> >
> > ---------------------------------------------------
> > PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
> > To subscribe, unsubscribe, or to change your mail settings:
> > http://lists.phxlinux.org/mailman/listinfo/plug-discuss
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/mailman/listinfo/plug-discuss




-- 
A mouse trap, placed on top of your alarm clock, will prevent you from
rolling over and going back to sleep after you hit the snooze button.

Stephen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20140730/856cfcc3/attachment.html>