Like you say, when you open reopen the app it has to reconnect to the proxy_orb which is why the splash-screen gets displayed. I'm wondering if the reconnect can be bypassed somehow.
When RoamingOrb is backgrounded maybe it can tell the core "i've been backgrounded" so that the core doesn't think it's dead when it stops responding to pings (I'm assuming this is how the protocol currently works). When re-opening RoamingOrb, the app can resume functioning as if it was never closed (maybe it just does a screen refresh).
Again, I don't know the details of the communication protocol, so this may be impossible without major structural changes. Thanks for listening to my ideas!
When RoamingOrb is backgrounded maybe it can tell the core "i've been backgrounded" so that the core doesn't think it's dead when it stops responding to pings (I'm assuming this is how the protocol currently works). When re-opening RoamingOrb, the app can resume functioning as if it was never closed (maybe it just does a screen refresh).
Again, I don't know the details of the communication protocol, so this may be impossible without major structural changes. Thanks for listening to my ideas!
Hmmm ... When you start the app it opens a connection to the core and that connection keeps open until you exit the app, or until it is broken (example: quick reloading the dce router).
What i probably could do is backgrounding the app and keeping the connection open (not sure if that is possible as long as i don't have a corresponding device). But you have to keep in mind that the app can also be used over 3G where disconnections are not rare.
Anyhow, i will investigate in that direction as soon as i have a multitasking enabled device ....



