Linked by Thom Holwerda on Thu 4th Jun 2009 11:57 UTC
Thread beginning with comment 367011
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2006-01-01
In theory tasks that run in the background can effect battery life. Practice has shown many times it doesn't effect battery life significantly.
Only one task can be the foreground application in every major OS with a GUI. Anything not running in the foreground (with focus) is running as concurrently as a background process would. There's little difference, other than the fact that most background processes are not displaying their UI.
But you're right, multitasking is not the same as running processes in the background (or indeed concurrently.) A process can be made up of one or more threads. Processes, by definition, will use at least one thread, but potentially more that that. There is nothing within the iPhone SDK that prevents multithreading, nothing at all. But multithreading is not the same as running multiple processes; I believe this is where your argument is a little confused?