Hi,

I am using v.2.0.1 also you can search for sources. Only that I need to do
is following:
1. I have my own client as follows:
/**
* Lite XML RPC client that reuse its transport for more request. Therefore
this
* class is not threadsafe!
*/
public class LiteClient extends XmlRpcClientLite {

  private XmlRpcTransport transport = null;

  public LiteClient(URL url) {
     super(url);
  }

  @Override
  protected XmlRpcTransport createTransport() {
     if (transport == null) {
        transport = new LiteTransport(this.url);
     }
     return transport;
  }

}
2. I have to copy LiteTransport because (if I remember good) it was not
public.
3. Switch on keepalive not to close the connection after request.

I am not sure if Lite* is included in v3.0, but at least you can see how I
manipulate it to get this behavior.
Hope it will help.

Stano
On 6/29/07, Don Montealegre <[EMAIL PROTECTED]> wrote:

hmm tnx!

    can u point me to which part i should use or manipulate even if your
using the old version? so that at least i will have an idea . thanks again
:)
----- Original Message -----
From: "Stanislav Miklik" <[EMAIL PROTECTED]>
To: <xmlrpc-dev@ws.apache.org>
Sent: Friday, June 29, 2007 5:48 PM
Subject: Re: XmlRpcClient persistent connections


> Hi,
>
> I think you can manage createTransport of the client always to return
> transport that will keep only one connection.
> I am using something like that but I am using the old (2.xxx) version of
> XML
> RPC and LiteTransport with keep-alive, but I assume that something like
> that
> is possible also in the new one.
>
> Regards
> Stano
>
> On 6/29/07, Don Montealegre <[EMAIL PROTECTED]> wrote:
>>
>> greetings ,
>>
>>     is there a way to just open and use 1 connection using XmlRpcClient
>> and just pass multiple request to it? tnx
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to