Right on!!!!
I also have been asking for this for a year now.
On Mon, 21 Aug 2000, Jeffrey Altman wrote:
> > > I'd prefer to bypass all OpenSSL-internal buffering and I/O entirely,
> > > and let the app do all the buffering and I/O.
> >
> > Maybe, but I'm not sure what you mean exactly. Could you describe
> > in terms of an approximate example API?
>
> I think what he would like is the ability to do what the Microsoft
> SSPI does. Instead of OpenSSL being a layer between the I/O channel
> and the app, he would like the app to provide all I/O functions and
> have OpenSSL provide routines that encode and decode buffers provided
> to it by the application. After OpenSSL has done its work, the
> application transmits the outgoing data to the peer. After receiving
> data from the peer it calls OpenSSL to process it.
>
> Its a different model which has its advantages when working with
> applications that may not have direct access to the network socket and
> instead have its I/O handle by message passing.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
