Or one could want default serialized execution on 3.0 and prior, in case of issues in third party code.
Looking at this more broadly, this is where I consider the framework somewhat lacking. It contains ready to use solutions for a lot of things, and using them is generally very simple and gets things done quickly. But attempts to customize something or to work around a bug often end at a "@hide" or "final" class or method. 21.04.2012 14:19 пользователь "b0b" <pujos.mich...@gmail.com> написал: > > > On Saturday, 21 April 2012 05:39:30 UTC+2, William Ferguson wrote: >> >> The real problem that is see with this change is that while you can >> modify all of your own uses of AsyncTask to suit you can be entirely >> hamstrung by one or more 3rd-party libraries that are also using AsyncTasks. >> >>> >>> > This concern could have been addressed with a single line of code, if > this private API had been made public: > > AsyncTask.setDefaultExecutor(AsyncTask.THREAD_POOL_EXECUTOR); > > But in infinite wisdom, it was decided that developers would use (or > abuse) above API wrong and thus this API was made private. > So instead of a single line change, if you want the Threaded Executor for > all your AsyncTasks you have to find and modify all your execute() calls. > > > -- > 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 -- 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
