On Friday, April 20, 2012 12:29:24 PM UTC-7, Mark Murphy (a Commons Guy) wrote: > > On Fri, Apr 20, 2012 at 3:16 PM, Nathan wrote: > > If I understand right, the default behavior of execute is changing to one > > single thread pool with only one thread? > > I have not been able to confirm that this change is in place. When I > try testing a bunch of tasks, they seem to execute in parallel, even > on 4.0.3 (haven't tried 4.0.4 yet). > I don't download the source myself, but if this source listing is accurate, it must be fully in place.
https://github.com/android/platform_frameworks_base/blob/master/core/java/android/os/AsyncTask.java > Yes. Either use the supplied pooled executor with executeOnExecutor(), > or move one of those things out of AsyncTask (e.g., > DownloadDictionaryTask might be better as an IntentService, if it is > supposed to keep rolling even if the user leaves the app). > I sure hope they won't be messing with the threadpool for intentservices too. Nathan -- 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
