And it is worth adding that not only is it buried in the firmware somewhere, but that it is subject to change without notice as Google decides on (they hope) a better way of doing it. Developers should consider this implementation (not interface) and not make any assumptions about it: let the system do its work.
On Aug 23, 2:42 am, Mark Murphy <mmur...@commonsware.com> wrote: > On Mon, Aug 23, 2010 at 5:36 AM, Arindam Ghosh <arindam2gh...@gmail.com> > wrote: > > Thank you for your reply..You mention Processes are > > cached for potential reuse.. What does it means.. > > It means what it says: processes are cached for potential reuse. Some > time in the future, when Android needs a new process, it may use one > out of the cache. The details of when and how it decides to use cached > processes is buried in the firmware somewhere. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > _The Busy Coder's Guide to Android Development_ Version 3.1 Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
