I think for most mobile applications you probably only want one download thread in order to prevent saturation of the (possibly slow) network connection. This thread could simply use a BlockingLinkedQueue to serialize the incoming requests. You'd also want to set aggressive timeouts on the HttpClient to prevent one stalled download from gumming up the queue.
I've found that this is actually a kind of difficult problem to solve very well, and not all applications have the same requirements. If you want to cache, persist, have fast downloads, and be error tolerant, you may end up writing a lot of code to suit your specific needs. :-( Doug -- 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
