Currently, the XmlRpcClient and XmlRpcClientLite use a simple
implementation of an http client. This implementation does not support
many extended HTTP features. I am currently working on a change to the
code that will enable this functionality, so possibly look for it in a
future release!
--Ryan Hoegg
John Perrotto wrote:
>Hi All,
>
>I'm using an HttpServlet to host my XmlRpcServer. I want to enable the
>HTTP keep-alive feature between my client and server apps. I've called
>the method XmlRpc.setKeepAlive(true) on the server and client-side. My
>Java client is using the
>org.apache.xmlrpc.XmlRpcClient.SecureXmlRpcClient and indeed the HTTP
>header being sent in the client request contains "connection -
>Keep-Alive" BUT it appears that a new connection is being made by the
>client with each request. The same thing is happening as well if I use
>an XmlRpcClient or XmlRpcClientLite client object. The funny thing is
>that I also have a COM based client application that's hitting this same
>XmlRpc Servlet and it's working properly reusing the same connection.
>Does anybody have any clues or suggestions? Am I missing some
>configuration parameter? Could there be a problem with any of these
>Apache client implementations? Thanks in advance for you help!
>
>JohnP
>
>
>
|