Thread issues with connection manager

[GoogleCodeExporter]

What steps will reproduce the problem?
Building an app that uses multiple threads, each which can use a (new)
XMLRPCClient to make remote method calls. The HTTP connection manager tries
to reuse the connection, but fails since the default manager is not thread
safe.

The solution is to use a thread safe connection manager, and attach this to
the (default) HTTP client. This can be as simple as supplying the
ThreadSafeClientConnManager to the DefaultHttpClient constructor. (A
registry scheme is needed though...) A patch is included.

What version of the product are you using? On what operating system?
Both today's SVN and the 0.2 downloadable version are affected.

Please provide any additional information below.
The supplied patch can be applied directly to the SVN and overrides the
connection manager used.

Original issue reported on code.google.com by erickok@gmail.com on 2 Jun 2009 at 9:50

Attachments:

• patch-threading.diff

[GoogleCodeExporter]

Thanks for this patch. I'll try and include it in the next release, however, it 
does
appear to conflict with changes proposed under ticket #17.

Original comment by JonTheNiceGuy on 30 Mar 2010 at 10:25

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Added under r17 (ages ago!).

Original comment by jon@sprig.gs on 19 Nov 2010 at 4:01

• Changed state: Done