Yeah, thats what I have done without the jingle exception (I use SIP for VoIP).
I think a simple buffer protocol would do, with a way of clients specifying what type of packets (like SIFT) which would cause a server flush... but due to the limitations on iOS that would probably only be Jingle. Regards Spencer On Tue, Oct 29, 2013 at 12:40 PM, Dave Cridland <[email protected]> wrote: > On Tue, Oct 29, 2013 at 12:29 PM, Spencer MacDonald < > [email protected]> wrote: > >> >>> 2) You will no longer receive VoIP Calls, which is the real purpose of >>>> the background socket. >>>> >>>> >>> Wouldn't mobile push solutions handle that if properly integrated? >>> >> >> The issue is that push notifications take anywhere between 1 and 20 >> seconds to reach a device under normal circumstances, so by the time the >> recipient sees the notification, launches the app, the app connects to the >> server etc the callee has probably hung up. >> >> > Oh. That's a bit pants, then. > > It'd be easier to solve these problems if the overriding concerns were > technical, of course, but it's looking like you'll need to handle a case > where pretty much all traffic is fully buffered, except for Jingle > session-initiate. > > We can call it Broken Apple Mode. > > Dave. >
