AsyncTask carefully makes no guarantee about how the work queue is handled. The problem with the current pool is that it can lead to subtle threading bugs in apps (and we've seen them) and there's no good way to fix them and still use AsyncTask.
On Fri, Feb 4, 2011 at 10:56 AM, Mark Murphy <[email protected]>wrote: > On Fri, Feb 4, 2011 at 1:52 PM, Romain Guy <[email protected]> wrote: > > The Honeycomb preview uses a serialized queue to execute AsyncTasks, so > they > > will execute one after the other. > > Is this a temporary thing? If not, that is a pretty major change, > rolling all the way back to Android 1.5-era functionality. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > _The Busy Coder's Guide to *Advanced* Android Development_ Version 1.9 > Available! > > -- > 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
