They are also WAY more overhead than just doing things in the local process (you need to do an IPC to the system, it needs to schedule the broadcast, then do an IPC back to each application that is receiving it, copying all of the data in it each time). For stuff happening in the local process, Handler and direct callbacks are the preferred approach.
On Wed, Sep 9, 2009 at 5:42 AM, Mark Murphy <[email protected]> wrote: > > Android Development wrote: > > Is it feasible to use a BroadcastReceiver as a glue layer between the > > user interface and the underlying business logic ? > > Yes, but bear in mind that broadcast Intents are not private. Anyone who > figures out an appropriate Intent filter can "listen in". Depending on > the nature of your application, this may or may not be acceptable to you. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://twitter.com/commonsguy > > Need help for your Android OSS project? http://wiki.andmob.org/hado > > > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
