Thank you for your quick reply. I thought about the PendingIntent, but in this application the information is only useful to the Caller if it is received while the Caller is active that time. So if the information arrives later, we'll still process it in the Service and store it for later use, but we don't want to invoke an activity in the Caller.
- John On May 6, 12:54 pm, Dianne Hackborn <hack...@android.com> wrote: > How about doing option 1, but having the caller include a PendingIntent for > where the result should be sent. This way the caller doesn't even need to > stick around while your service is running -- it can give you a > PendingIntent that launches a receiver when you send it back. > > If you want to go the IDL route, I would suggest an async call, with a > callback interface that is suppled and you call when done. > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
