I found the same issue (actually, response-content from a previous request was 'bleeding' over into the next one).
I solved this by make an AndroidHttpClient a ThreadLocal. This way, the number of AndroidHttpClients is never larger than the number of threads handling http-requests in the background. And if you use AsyncTask or ExecutorService, you'll never have more than a small and fixed amount of threads(AndroidHttpClients). When a thread is re-used for a http-request, the existing AndroidHttpClient for that thread (ThreadLocal) is re-used as well. -- 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
