Er... there is NO reason to use sticky broadcasts for communication within your own app. In fact, I'll go farther and say you just should not do this. Sticky broadcasts are GLOBAL to the system. And because of this, performing a sticky broadcast is multiple orders of magnitude slower than just implementing direct calls within your own app (IPC for each receiver to register, IPC to the system to send it, IPC from the system back to your app to deliver it, marshalling and unmarshalling of all the data within the Intent over both IPCs).
More than that, there is NO protection on them, so any other application can watch your sticky broadcasts, or even send their own values back to you. (Btw, this is also issue with using any broadcasts within your own app. Broadcasts are really there for cross- application communication. It is just far more efficient and easier to implement these things within an app by having a callback interface.) Now I am really regretting that I made that function public. :/ > And of course, if you want out of application notifications, you have > no other option. You do have the option of using a normal broadcast rather than a sticky broadcast. You'll notice that there are basically no sticky broadcasts used by the system, at least that you see in the public APIs. In fact there are some places they are used internally, but even those are slowly going away as we discover security holes with them because there is no way to protect who can receive the broadcast data. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
