RE: Non-blocking connect: getsockopt fails

2009-07-16 Thread David Schwartz
Rij wrote: > getsockopt fails with the message: "Invalid argument" which is EINVAL. Which means that one of the arguments is invalid. > next. What argument is invalid? The only thing that I am suspicious > about is the socket descriptor. Is it ok? optval and optlen are both > int. Did you set

Non-blocking connect: getsockopt fails

2009-07-16 Thread Rij
Hi All, I am trying to write a non-blocking client. Based on previous threads that I have read on this forum, I have adopted the following strategy. 1) Get a new BIO object. 2) I set the BIO to be non-blocking. As I understood from the manual, I set it to non-blocking just before calling BIO_do_c