Ivan wrote: > The experience I shared there was practical - and there are times and > requirements when you do need to start a service at the boot time, and > it's really better to run it in a separate process. For example, any > mail-like application would have such requirements.
There is absolutely no reason why the activity for a mail client would need to run in a separate process from the service handling the mail protocol. By using android:process=:remote, you are going to force those to be in separate processes unnecessarily, consuming a lot of extra RAM along the way. With respect to having the service component of a mail application run forever, I would really recommend polling at least as a option for users who do not wish your service to attempt to run forever. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android App Developer 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
