Option #1 is a lot more intrusive. You lose the ability to automatically switch layouts, drawables, etc. It might be fine now but it might come back to bite you in the future. It should always be your last resort. Saving and restoring an AsyncTask is not difficult.
On Fri, Sep 10, 2010 at 8:56 AM, Bret Foreman <[email protected]> wrote: > Yeah, Mark's option 1 looks like the best approach for my application. > Android should provide more infrastructure for this sort of thing > because async web services are becoming almost universal and they > always require something like this when they interact with the UI. > > -- > 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 > -- Romain Guy Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support. 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
