That's why AsyncTask now lets you execute tasks on your own thread pool. On Fri, Feb 4, 2011 at 11:51 AM, Shane Isbell <[email protected]>wrote:
> > > On Fri, Feb 4, 2011 at 11:24 AM, Streets Of Boston < > [email protected]> wrote: > >> Why do i really really really want a serialized queue? >> Our app uses AsyncTasks to complete HTTP requests. Multiple requests >> can happen at the same time and in some situations we really really >> really want it that way. As long as the onPostExecute is called >> correctly, it should not be a problem.... >> > It really depends on the app. I've encountered problems with AsyncTask on > some apps. I had to replace the queue implementation in the AsyncTask for it > to work. Later when I customized the HttpUrlConnection to account for some > threading problem, I found the original queue in AsyncTask worked fine. > Something there seems a little goofy. > > Shane > > -- > 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
