Apple push notification for iPhone works when the app is closed. In that case the iPhone client is not able to pull data. Meanwhile users want any mentions or DMs to pushed to them when the iPhone client is closed. So we must use a server to check DM & Mentions for users.
On Aug 21, 8:10 pm, Andrew Badera <and...@badera.us> wrote: > If you're already talking about a 2-minute delay, then why "push" and > not "pull" ?? Polling clients will give you greater scalability with > that range of latency easily achievable for little investment.Pushis > meant for immediate notifications. Truepushto 500k+ clients is > costly -- but you don't need millisecond latency here. Pull is much, > much cheaper. > > ∞ Andy Badera > ∞ This email is: [ ] bloggable [x] ask first [ ] private > ∞ Google me:http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera) > > > > On Fri, Aug 21, 2009 at 8:07 AM, Dewald Pretorius<dpr...@gmail.com> wrote: > > > In addition, your database will have to cope with 8,300 writes per > > second. And then you need to take into account the latency of the > > ApplePushNotificationservice. > > > Dewald > > > On Aug 21, 8:57 am, Dewald Pretorius <dpr...@gmail.com> wrote: > >> On Aug 21, 12:06 am, "ke...@nibirutech.com" <intelligent...@gmail.com> > >> wrote: > > >> > What if we have a large user base, say , 500, 000 users at > >> > least? How can we use a proper solution to get a 2-minutes delaypush > >> > for any user's mentions and DMs? (we can't afford the server cost for > >> > half million requests every 2 minutes) > > >> You are actually talking about one million API calls every 2 minutes > >> (1 for mentions, one for DMs). > > >> That's 8,300 API calls per second. > > >> My rough estimate is that you are going to need around 200 servers to > >> cope with that workload. > > >> Dewald