i hope not, because the code makes a new HttpClient instance per
ArtRetrievalTask. i suppose it could be trying to be clever,
realising that the requests are going to the same place, and
utilising HTTP 1.1 to bundle the requests into the same connection.
if that's really what's happening (and i suspect not, somehow), and
maybe only the server logs can tell for sure, then i hereby state for
the 67th time how happy i am that i dumped HttpClient and rolled my
own HTTP.
Perhaps the requests are being serialized by HttpClient? I wonder if
there's a way to determine the actual thread a particular
AsyncTask's doInBacground process runs on, like maybe a thread id?
--
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>http://groups.google.com/group/android-developers?hl=en
--
jason.vp.engineering.particle
--
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
