On Thu, Nov 4, 2010 at 1:00 PM, Kostya Vasilyev <[email protected]> wrote:
> However, it's not out of the question that calling sendBroadcast, with it > being a framework function, is only allowed from the UI thread, just like > many other framework functions in Android. > sendBroadcast can be called from any thread. There are no issues I know of with sendBroadcast dropping broadcasts, outside of the expected behavior I mentioned earlier. IntentService itself is extremely simple, and just enqueues each onStartCommand() to a handler. It is very unlikely things are being lost at that point. An interesting test case showing a problem would be something that derives directly from Service, showing that a call to startService() does not result in the given Intent appearing in Service.onStartCommand(). -- 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
