Michael Elsdörfer wrote: > I have a service that runs continuously. Please try to avoid that. This is why users attack us with task killers.
http://www.androidguys.com/2009/09/09/diamonds-are-forever-services-are-not/ http://www.androidguys.com/2010/03/29/code-pollution-background-control/ > Is there actually any gain here? if Android frees the memory of > finished Activities anyway, is there any benefit to using a separate > process, or is it maybe making things worse, even? While the client is up, two processes will make things worse. > I can't help but notice that no other app seems to use a remote > process, including builtin one's like Google Talk or the Music Player. > I'm I correct in assuming that this is the recommended approach then? Avoiding multiple processes is right up there with avoiding everlasting services -- in this case, avoidance is a good thing. :-) -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android Training...At Your Office: http://commonsware.com/training -- 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 To unsubscribe, reply using "remove me" as the subject.
