NAME
bio - I/O abstraction
SYNOPSIS
#include
TBADESCRIPTION
A BIO is an I/O abstraction, it hides many of the underlying I/O details from an application. If an application uses a BIO for its I/O it can transparently handle SSL connections, unencrypted network connections and file I/O. There are two type of BIO, a source/sink BIO and a filter BIO. As its name implies a source/sink BIO is a source and/or sink of data, examples include a socket BIO and a file BIO. A filter BIO takes data from one BIO and passes it through to another, or the application. The data may be left unmodified (for example a message digest BIO) or translated (for example an encryption BIO). The effect of a filter BIO may change according to the I/O operation it is performing: for example an encryption BIO will encrypt data if it is being written to and decrypt data if it is being read from. BIOs can be joined together to form a chain (a single BIO is a chain with one component). A chain normally consist of one source/sink BIO and one or more filter BIOs. Data read from or written to the first BIO then traverses the chain to the end (normally a source/sink BIO).SEE ALSO
BIOctrl(3), BIOfbase64(3), BIOfbuffer(3), BIOfcipher(3), BIOfmd(3), BIOfnull(3), BIOfssl(3), BIOfindtype(3), BIOnew(3),BIOnewbiopair(3), BIOpush(3), BIOread(3), BIOsaccept(3),
BIOsbio(3), BIOsconnect(3), BIOsfd(3), BIOsfile(3),
BIOsmem(3), BIOsnull(3), BIOssocket(3), BIOsetcallback(3), BIOshouldretry(3)0.9.7l 2001-04-12 bio(3)