diff options
author | Dr. Stephen Henson <steve@openssl.org> | 2000-09-11 01:04:09 +0000 |
---|---|---|
committer | Dr. Stephen Henson <steve@openssl.org> | 2000-09-11 01:04:09 +0000 |
commit | b1ccd57b18c4c2ea6f1a1199c3afdd33eb070baa (patch) | |
tree | b75eb440fe6129dfeabb6c17bbc0186c2af3c567 /doc/crypto/BIO_s_null.pod | |
parent | 5fd0cd9a9b7ee101c93719b01c5fccf2ae5cee99 (diff) |
Docs for cipher and base64 BIOs.
Diffstat (limited to 'doc/crypto/BIO_s_null.pod')
-rw-r--r-- | doc/crypto/BIO_s_null.pod | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/crypto/BIO_s_null.pod b/doc/crypto/BIO_s_null.pod index b9a3c2cf3f..c64c9838bc 100644 --- a/doc/crypto/BIO_s_null.pod +++ b/doc/crypto/BIO_s_null.pod @@ -13,7 +13,7 @@ =head1 DESCRIPTION BIO_s_null() returns the null sink BIO method. Data written to -the null sink is discraded, reads return EOF. +the null sink is discarded, reads return EOF. =head1 NOTES @@ -24,9 +24,9 @@ A null bio can be placed on the end of a chain to discard any data passed through it. A null sink is useful if, for example, an application wishes to digest some -data but not write the result anywhere. Since a BIO chain must normally -include a source/sink BIO this can be achieved by adding a null sink BIO -to the end of the chain +data by writing through a digest bio but not send the digested data anywhere. +Since a BIO chain must normally include a source/sink BIO this can be achieved +by adding a null sink BIO to the end of the chain =head1 RETURN VALUES |