On 9 June 2010 00:02, Streets Of Boston <flyingdutc...@gmail.com> wrote: > "However, that approach can still lose responses or duplicate network > usage if the Activity is destroyed/created while the AsyncTask is > doing its job" > > Is that an issue with the Droid-fu or with AsyncTask? > I don't have that issue. When configuration changes take place, no new > requests are duplicated and existing ones just keep going, as long as > you put the AsyncTasks in a static context (not an (activity) instance > context). > >
Maybe I'm making an assumption about how you are using AsyncTask, but what happens in the gap between the old Activity being destroyed and before the new one has been created. What happens to the result in that gap as you have no valid Activity to display the result? Either you are losing your response, or you have to re-request it (hence duplicate network usage). Or I guess you could be storing the result temporary in your Application class? Andrew -- 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
