On Sun, Mar 18, 2012 at 9:50 PM, OldJim <junderw...@ipass.com> wrote: > Why should he not do that?
Because he is decreasing reliability while at the same time wasting RAM, CPU, and battery. > Are you saying that the Android Delayed Message is not reliable? It is reliable *so long as the process is around*. For it to work, the process must stick around indefinitely: the everlasting service anti-pattern. There are cases where you truly do need a service to try to live forever (e.g., non-SIP VOIP client), but those are few and far between. The vast majority of everlasting services are a waste of RAM, CPU, and battery. Such services materially impact Android's success, as users get very very tired of having to go in and get rid of the damn things. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 2.5 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
