3 ms·
Unless I'm greatly mistaken (completely possible) symbian is a more traditional multi-tasking system. The UI and everything else was more or less kept in memory
by enjo 17y ago
Unless I'm greatly mistaken (completely possible) symbian is a more traditional multi-tasking system. The UI and everything else was more or less kept in memory with the only caveat being that you had to learn to graciously deal with being shutdown as memory ran low.
I also think that the Apple system varies pretty significantly from Android. Android has the concept of 'bundles' and 'servers'. Bundles work similarly to what Apple is doing, but having servers (which multi-task in a more traditional model) enables more consistent background processing.
For instance, an alarm clock on Android is often implemented with the GUI 'bundle' on the front-end and a server on the back-end that manages the actual 'when should I sound the alarm?' part of the task.'
That's one thing that just isn't possible in the iPhone model.
- wvenable 17y agoI doesn't sound like there is any way for the iPhone OS to selectively unload parts of an app. So, just like Symbian (and every other platform), the entire app stays in memory. The big difference with the iPhone is that there isn't any background threading except when triggered directly by the OS for a specific purpose. That's a fairly minor difference but it would prevent poorly written apps from eating up too much battery life (or doing other nasty things in the background). Having to graciously deal with being shutdown (and restore your state on relaunch) is pretty much the same model as the iPhone OS 4.
- blasdel 17y agoI'd be surprised if the new "Local Events" API didn't offer a cron-like scheduling system.