Jim Segrave wrote:
Why not simply create a second socket - your app reads from that, does whatever is needed and writes to the openssl socket. When openssl writes to its socket, you read it, do whatever, then write it out your socket?
Jim, for me the main goal to replace functions that operate with sockets is performance. I want to use OpenSSL with Windows IO Completion ports. The method that you suggest is very interesting but the main is not achieved - OpenSSL is still writing to the socket. Besides we got so-called "double buffering" and also more memory usage because of 2 sockets.
______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
