With multi-tasking enabled, can I safely throw away tombstoning when porting my project to Mango?
With multi-tasking enabled, can I safely throw away tombstoning when porting my project to
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
With multi-tasking enabled, can I safely throw away tombstoning when porting my project to Mango?
Fast app switching is where the app is deactivated, but is not tombstoned. It now goes into a dormant state. If memory is required, the app may be tombstoned from this dormant state. If the app is activated and it is in the dormant state, it is merely activated and continues running as if nothing really happened (you will need to reconnect any sockets, re-acquire the camera, etc if required). If the app was tombstoned, it goes through the same re-activation as apps currently do.
Multitasking where is the new background agents come into play. Background agents are a separate assembly distributed with your app that can be set to run while your app is not running. They will get 15 seconds of execution time every 30 minutes (as long as those figures haven’t changed since the announcement at MIX11) for up to two weeks.
From here.
Also: From Tombstoning to Fast Application Switching