This is pretty standard - if I understand you correctly, you mean that you have a client that keeps a pool of sockets connected to a particular server. You just need to implement some way of storing the session ids from the handshake using say SSL_get1_session (), and then setting these back ito the session when you re-connect using SSL_set_session ().
does this help any? Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Harald Ommang Sent: 19 July 2003 10:49 To: [EMAIL PROTECTED] Subject: RE: Connection pool for HTTPS using OpenSSL On Wed, 16 Jul 2003 14:49:41 +0100, "steve thornton" wrote: > > Sorry, can't read - you mean server. If you set up a session caching sceme, > then maintaining a pool of connections is cheap (ish) and straightforward. I > have code snippets if you need them > > Steve Hehe, well if you can't read, then I can't write :-) Cause I mean creating a *client* that has a pool of connections against the web server I will be communicating with. And yes, snippets would be very welcome, as I am new to OpenSSL. Harald ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
