Lines Matching +full:3 +full:a

15 A BIO is an I/O abstraction, it hides many of the underlying I/O
16 details from an application. If an application uses a BIO for its
20 There are two types of BIO, a source/sink BIO and a filter BIO.
22 As its name implies a source/sink BIO is a source and/or sink of data,
23 examples include a socket BIO and a file BIO.
25 A filter BIO takes data from one BIO and passes it through to
27 example a message digest BIO) or translated (for example an
28 encryption BIO). The effect of a filter BIO may change according
33 BIOs can be joined together to form a chain (a single BIO is a chain
34 with one component). A chain normally consists of one source/sink
36 first BIO then traverses the chain to the end (normally a source/sink
42 and frequently a utility function exists to create and initialize such BIOs.
44 If BIO_free() is called on a BIO chain it will only free one BIO resulting
45 in a memory leak.
47 Calling BIO_free_all() on a single BIO has the same effect as calling
50 Normally the I<type> argument is supplied by a function which returns a
51 pointer to a BIO_METHOD. There is a naming convention for such functions:
52 a source/sink BIO typically starts with I<BIO_s_> and
53 a filter BIO with I<BIO_f_>.
57 Create a memory BIO:
63 L<BIO_ctrl(3)>,
64 L<BIO_f_base64(3)>, L<BIO_f_buffer(3)>,
65 L<BIO_f_cipher(3)>, L<BIO_f_md(3)>,
66 L<BIO_f_null(3)>, L<BIO_f_ssl(3)>,
67 L<BIO_f_readbuffer(3)>,
68 L<BIO_find_type(3)>, L<BIO_new(3)>,
69 L<BIO_new_bio_pair(3)>,
70 L<BIO_push(3)>, L<BIO_read_ex(3)>,
71 L<BIO_s_accept(3)>, L<BIO_s_bio(3)>,
72 L<BIO_s_connect(3)>, L<BIO_s_fd(3)>,
73 L<BIO_s_file(3)>, L<BIO_s_mem(3)>,
74 L<BIO_s_null(3)>, L<BIO_s_socket(3)>,
75 L<BIO_set_callback(3)>,
76 L<BIO_should_retry(3)>
83 this file except in compliance with the License.  You can obtain a copy