I probably need to look at the code but am I right is saying that the connection will stay alive as long as data is sent across the socket. It data is not sent for more than 45 seconds the socket connection timeouts. The next time data is sent the SSL handshaking happens again. This delay is not acceptable for my application so I perform a ping every 10 seconds to keep the session alive. It the socket could be configured not to timeout I would not need this ping. Or if JSSE support SSL session reuse over TCP/IP reconnects like OpenTLS does.
Tim McClure -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 03, 2002 3:30 AM To: [EMAIL PROTECTED] Subject: Re: RE: Secure xmlrpc is, XmlRpc.setKeepAlive(true); not enough for you here ? cheers. ------------------------ [EMAIL PROTECTED] wrote: ------------------------ >I am currently implementing SSL using XML-RPC with success. However I have >to write a ping method to ping the WebServer class every 10 seconds so that >my connection does not timeout. If I allow my session to time-out I have to >go through the handshaking again. My question is can get rid of the ping by >having the following: >1. Allow the WebServer class to have a configurable socket time out. >2. Is there a way for JSSE to reuse SSL sessions across TCP/IP >connections? > >Tim McClure >GE-Interlogix >(561) 439-8789 > >-----Original Message----- >From: Rogers, Mike [mailto:[EMAIL PROTECTED]] >Sent: Wednesday, October 02, 2002 3:27 PM >To: '[EMAIL PROTECTED]' >Subject: RE: Secure xmlrpc > > >I learn something new each day. Thanks! > >---- >Mike Rogers >Director, (Technology)3 >203-352-0752 > >> ---------- >> From: Ryan Hoegg >> Reply To: [EMAIL PROTECTED] >> Sent: Wednesday, October 2, 2002 3:29 PM >> To: [EMAIL PROTECTED] >> Subject: Re: Secure xmlrpc >> >> Rogers, Mike wrote: >> >> >For the client, org.apache.xmlrpc.XmlRpcClient uses >> java.net.URLConnection >> >to make the connection. I'm not sure whether or not this can perform a >> >secure connection. What ever you use to make this connection will need to >> >support SSL. That should take care of it. >> > >> Well, in the current version of the code you will want to use >> SecureXmlRpcClient instead of XmlRpcClient. I am working on some >> changes to XmlRpcClient that will make it work the way the original >> poster mentioned, just using https in the URL. >> >> Watch for this in a future version of HttpClient. >> >> -- >> Ryan Hoegg >> ISIS Networks >> >> >
