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
Hi
We are using the Apache XML-RPC client for interfacing with an XML-RPC
server implemented using Python. We want to improve the communication
performance by setting up a single TCP connection and send all the xmlrpc
calls over this single connection.
We are using the
On Tue, Jan 13, 2009 at 7:37 PM, Yanwar Asrigo asrigoyan...@gmail.com wrote:
In my simple code, I created the xmlrpc client and then execute two xmlrpc
calls using this client. However, from what I see from the log, it seems
that the client reopen a new connection for the second execution.
Yes the server does offer the keepalive as I have modified it so.
I will check the XmlRpcSunHttpTransport too in that case.
Thanks!
On Tue, Jan 13, 2009 at 3:25 PM, Jochen Wiedmann
jochen.wiedm...@gmail.comwrote:
On Tue, Jan 13, 2009 at 7:37 PM, Yanwar Asrigo asrigoyan...@gmail.com
wrote:
On Wed, Jan 14, 2009 at 4:11 AM, Yanwar Asrigo asrigoyan...@gmail.com wrote:
Yes the server does offer the keepalive as I have modified it so.
Did you verify that by looking into the output of tcpmon or wireshark?
Jochen
--
I have always wished for my computer to be as easy to use as my
