Controlling OpenSSL's use of read() and write()

2005-05-25 Thread Hrvoje Niksic
Does anyone know if it is possible, and how, to control the way OpenSSL communicates with the remote host? Wget normally precedes each read() and write() with a select() that enforces the idle timeout specified by the user using --read-timeout and --timeout. In SSL it is not enough to select()

Re: Controlling OpenSSL's use of read() and write()

2005-05-25 Thread Daniel Stenberg
On Wed, 25 May 2005, Hrvoje Niksic wrote: In SSL it is not enough to select() before SSL_read because SSL_read can and does call read multiple times, which breaks the intended timeout semantics. Is there a way to prevent this? I figure one way is to use non-blocking sockets, isn't it? --

Re: Controlling OpenSSL's use of read() and write()

2005-05-25 Thread Hrvoje Niksic
Daniel Stenberg [EMAIL PROTECTED] writes: On Wed, 25 May 2005, Hrvoje Niksic wrote: In SSL it is not enough to select() before SSL_read because SSL_read can and does call read multiple times, which breaks the intended timeout semantics. Is there a way to prevent this? I figure one way is