After reading the thread regarding AsyncTask and Activity configuration changes, I am actually a bit more skeptical now than when I started!
http://groups.google.com/group/android-developers/browse_thread/thread/e1d5b8f8a3142892?pli=1 With respect to the one-and-done off-UI thread task, is there a best usage pattern? The AsyncTask has an affinity with its host Activity, making it a nice solution, however for the reasons cited in the above post, it may be too brittle. IntentService dispenses with the configuration changes but leaves you in a lurch when requiring a response. I'm sure the other off-UI thread techniques bring their own idiosyncrasies when the host Activity could die and be resurrected while they are off working on behalf of the now deceased activity. BTW, should we consider the Looper/Handler technique deprecated for this use case? Peace, Scott -- 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
