The first paragraph of http://developer.android.com/guide/topics/fundamentals.html#procthread indicates that anytime the FIRST component (activity, contentprovider, service, bcastrcvr) needs to run, a new Linux process is created for the app. If the process is killed, then the components have no place to run, so in my opinion it is not possible to retain the app when its underlying process has been killed.
However, the next paragraph of the above document indicates that components of an app can be setup to run on more than one processes. So, theoretically it is possible to arrange an app with M+N components to run on two processes P and Q where P runs M components and Q runs the remaining N components. If P is killed, then the M components will get wiped out, but the other N components still run on the second process Q... nevertheless a process is needed to run these remaining N components. My two cents.... I may be wrong and let's hear from the rest of the group. On Mar 15, 7:39 am, Fuzzyboy <[email protected]> wrote: > Being interested in Android development and still in the > experimentation phase - there's something I haven't been able to > grasp. > > As far as I've been able to understand, the process lifecycle and > applikation lifecycles are seperate and as such, it would be possible > for the application to still to exist, even if it's process has been > killed. > > So I guess my question would be, in what scenario could this occur and > how is the application accessible if the containing process has been > killed? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
