<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>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?</div><div><br></div><div>(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.)</div><div><br></div><div><blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto;">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%).<br><br>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.<br><br>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.<br><br>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.)</blockquote></div></blockquote></div><div><br></div><div>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.)</div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px;"><div>-David </div><div><br class="khtml-block-placeholder"></div><br class="Apple-interchange-newline"></span>
</div>
<br><div><div>On Jul 30, 2014, at 5:51 AM, Stephen Partington <<a href="mailto:cryptworks@gmail.com">cryptworks@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p dir="ltr">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. </p>
</blockquote></div><br></body></html>