On Feb 8, 11:25 pm, Al Sutton <[email protected]> wrote: > Thanks for the clarification Dianne. > > I'm guessing the confusion comes from people who (like me) are > familiar with the traditional Linux process model of when a process > has finished it dies
What constituents "finished" for an Andorid application? The Android platform starts processes that run JVMs to execute application components (a standard Unix/Linux pattern). The concept of a task, that can span across processes and activities, however is a pure Android concept. > > I'd read the process/threads section you've mentioned and in my mind > it read as a warning of what could happen if resources become tight as > opposed to it being the expected normal operation for all processes. My take is that it is "normal" for resources to be tight - including CPU resources which is why processes are not killed until necessary. > Might it be worth adding a line that explicitly states that it is > normal for processes to be left running when there they are not active That is already mentioned under "empty processes" -- 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
