Yes. But in the context of the original message, what is meant is that
OpenSSL should not directly address the comms (send/receive).
The solution for NT using I/O Completion Ports would be to handle the
I/O in the main code and simply pass peer or application data into the
'library' and to receive peer or application data from the 'library'.
I proposed a solution to this (with code). However, I would be
interested in other suggestions.
Ron.
> -----Original Message-----
> From: Ben Laurie [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, May 17, 1999 7:05 PM
> To: [EMAIL PROTECTED]
> Cc: Rick Harvey
> Subject: Re: IO Completion Ports and openssl
>
> Ron Ramsay wrote:
> >
> > We have a crypto server that uses OpenSSL as a library. (SSL *)
> contexts
> > are given memory BIOs for I/O. OpenSSL is driven by calls to
> SSL_read(),
> > SSL_write(), BIO_read() and BIO_write(). There are no sockets.
> >
> > I am attaching an archive containing the source code that implements
> > this API and a README file. This software is provided "as is". See
> the
> > README file for details.
> >
> > Please regard this as a work in progress. I am interested in seeing
> > OpenSSL evolve to a library.
>
> Pardon? Isn't it one already?
>
> Cheers,
>
> Ben.
>
> --
> http://www.apache-ssl.org/ben.html
>
> "My grandfather once told me that there are two kinds of people: those
> who work and those who take the credit. He told me to try to be in the
> first group; there was less competition there."
> - Indira Gandhi
> ______________________________________________________________________
> 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]
