> IMHO, just use AsyncTask for the HTTP requests. It already has a thread > pool, tuned for what the core Android team feels is a reasonable number > of threads for this sort of purpose. >
So you would suggest that I would create and start 20 async tasks, each responsible for one download, and let the Android Core take care of how many of them to run at once? I agree with using AsyncTask where it makes sense. This would fit the model, other than the fact that I am not starting on the UI Thread. Can AsyncTask be started on another thread? I also wonder, though, if the AsyncTask takes into account that each task might be running an HttpRequest since it is for general purpose threaded. I can foresee running out of HttpRequests before running out of threads, if there is a practical limit. 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
