Erik Hellman wrote: > Using > intents would require some re-design, which is fine by me but I'm > looking for the drawback of using this from a performance and power- > consumption point-of-view. Do broadcast intents consume more power > than direct service calls? Does sending, receiving and parsing a > broadcast intent take more CPU than a direct service call?
If you are creating a music player, playing music will take up much more CPU time and battery life than either communications mechanism, probably by a few orders of magnitude. Personally, I'd focus on other issues, such as usability of whatever third-party interface you're offering. > I know it is a very general question, but I'm assuming there is a > general guideline when to use intents and when to use a service? Not especially. I'm not aware of anyone publishing any sort of performance comparison, and both the AIDL and broadcast Intent stuff is deep enough in the code base as to be difficult to follow for us mere mortals. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 0.9 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 -~----------~----~----~----~------~----~------~--~---
