Hello. I am implementing openssl app which uses async windows sockets(nonblocking) and I am wondering whether openssl has any completion notification like a callback function to signal that the connection stage has been completed, or there is information ready to read. I cannot use Winsock IO Completion Ports (I am under win98).
The solution to SSL_ERROR_WANT_WRITE and _WANT_READ errors is just to call the function again, but in case of connection procedure, my app calls several thousands times the SSL_connect function, which I find not very "clean" solution as during this time the client blocks... So maybe there are some mechanisms which signal completion of these tasks? Once connected, the server's windows async sockets procedures start generating the FD_READ messages, which means that there is data to be read from the socket, but the SSL_read function all the time returns _WANT_READ error and this way the server blocks. How can I overcome that? Any help would be greatly appreciated. -- Tego nie znajdziesz w zadnym sklepie! [ http://oferty.onet.pl ] ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
