On Thu, Nov 4, 2010 at 5:36 PM, Matt Quigley <matthew.quig...@gmail.com> wrote: > Hi all. I have read all about having separate processes for different > Application components, and how to use them. I am curious, what are > some appropriate use cases for when an application should actually use > separate processes?
I'm not sure there are any for the vast majority of Android apps. > It seems to me, the main advantage to using > separate processes is to make the different portions of your app more > easily killable by the OS. No offense, but taking up double memory to allow the OS to more easily kill half of it is like chopping down trees to give you more paper for recycling. There might be valid reasons for using more than one process -- though I don't know of any -- but I feel fairly confident this is not one of them. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android 2.2 Programming Books: http://commonsware.com/books -- 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
