> IntentService dispenses with the > configuration changes but leaves you in a lurch when requiring a > response.
In addition to Mark's suggestions, you could assign a ResultReceiver to one of the Intent's extras: Your Activity could implemented this ResultReceiver's *onReceiveResult * method. Your IntentService could just call '*send(resultCode, resultBundle)*' on it. This will cause the onReceiveResult at the Activity's side to be called. -- 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
