First, thank you for your responses. I appreciate the feedback, but I
don't think I understand the points you are making in your last email.
Perhaps, I did not explain myself well enough, but the idea of allowing
long operations to be cancelled is hardly rare. Suppose for example, you
want to search for a friend in the phone book. Whatever criteria you
specify you are going to want to stop excessive search results from
continuing once you have found the person you are looking for.
Supporting that in a clear text mode, but not in an SSL mode doesn't
make sense.
It would seem that the SSL structure could be shared between reads and
writes if we could guarantee that they didn't use the same members of
the structure. Does anyone know which members are shared between both
reads and writes. I know the "rwstate" is, but I'm not sure what else.
Verdon
>>> [EMAIL PROTECTED] 3/19/2003 12:41:37 PM >>>
OpenSSL doesn't support cancelable operations simply because it
is
extremely rare that someone would want to use them. You may implement
your own buffering with asynchronous semantics if you wish. You could
also use OpenSSL BIO pairs for this purpose.
OpenSSL just can't give you the same semantics TCP does without
being integrated into the operating system.
DS
______________________________________________________________________
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]
