Beyond agreeing with what Mr. Hearn wrote, a few other points: Erik H wrote: > Also, is really an AIDL the right way to allow third-party > integration?
AIDL has a few huge advantages that may or may not be relevant to you: 1. You actually get return values. 2. You don't need your service running to use AIDL -- the bind operation can auto-start the service if it is not already running. 3. If you use binding to implicitly start your service, Android will shut down the service when there is nothing else bound to it. The combination of #2 and #3 means that I hope you can avoid the always-running service pattern. Use AIDL. If your service needs to do some work on occasion independent of any activity, use AlarmManager and WakeLocks to schedule the startup and execution of that work. After all, you're going to need them anyway, since phones go to sleep, so you may as well minimize your footprint as part of the bargain. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android 1.5 Programming Books: http://commonsware.com/books.html --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
