I haven't checked it using that. I was basing it on the wire log:
DEBUG [org.apache.commons.httpclient.HttpMethodBase] Resorting to protocol
version default close connection policy
DEBUG [org.apache.commons.httpclient.HttpMethodBase] Should NOT close
connection, using HTTP/1.1
DEBUG
I'm not sure if this helps with the discussion or not, but here goes.
I haven't paid much attention to what happens when using httpclient within the
xmlrpc framework, but around the days of httpclient v2.0, I used it extensively
in a standalone fashion. I did look at version 3.0 as well, but
yes, I have similar experiences with xmlrpc-2.x with using
XmlRpcLiteClient. This client for every request creates new transport
class, ie. new connection was created every time. Therefore I have to
create my new implementation :
public class LiteClient extends XmlRpcClientLite {
private
