On Wed, Feb 15, 2012 at 1:25 PM, A. Elk <[email protected]> wrote: > A continuously-running Service is not always bad. Sometimes this type of > Service is necessary.
For about one app in several hundred, perhaps. We have *way* too many cases of apps "leaking" services and *way* too many pissed off users as a result. I would rather developers be "fearful" of everlasting services than to use them indiscriminately. > For example, sync adapters use a service that's always running Do you have a reference for this? Since this whole sync area is pretty much undocumented (outside of drips and drabs of JavaDocs), I have no idea what to expect from implementations. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 4.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 [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
