Ahh, that is true. I didn't realize that you could close an "unopened" socket
like that. This makes sence. One of these days this will get implemented.
Sean Walker
Dingbat Designs
>You could start a secondary thread that sleeps for the desired number of
>seconds then close the socket (if the primary thread has still not succeeded
>in connecting). This should exit the primary thread socket call with an
>error.
>
>Nicolas Roumiantzeff.
>
>>Sean Walker wrote:
>>
>>> >That's what I was going to do too, but under Win32 you can't set the
>>> All of my research has said the same thing. I couldn't set the timeouts.
>If
>>> you can manage to figure it out, please post your solution! :)
>>>
>>> Sean Walker
>>> Dingbat Designs
>
>
>______________________________________________________________________
>OpenSSL Project http://www.openssl.org
>Development Mailing List [EMAIL PROTECTED]
>Automated List Manager [EMAIL PROTECTED]
>
>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
