| BIO_s_mem.pod (68652) | BIO_s_mem.pod (238405) |
|---|---|
| 1=pod 2 3=head1 NAME 4 5BIO_s_mem, BIO_set_mem_eof_return, BIO_get_mem_data, BIO_set_mem_buf, 6BIO_get_mem_ptr, BIO_new_mem_buf - memory BIO 7 8=head1 SYNOPSIS --- 60 unchanged lines hidden (view full) --- 69first, so the supplied area of memory must be unchanged until the BIO is freed. 70 71=head1 NOTES 72 73Writes to memory BIOs will always succeed if memory is available: that is 74their size can grow indefinitely. 75 76Every read from a read write memory BIO will remove the data just read with | 1=pod 2 3=head1 NAME 4 5BIO_s_mem, BIO_set_mem_eof_return, BIO_get_mem_data, BIO_set_mem_buf, 6BIO_get_mem_ptr, BIO_new_mem_buf - memory BIO 7 8=head1 SYNOPSIS --- 60 unchanged lines hidden (view full) --- 69first, so the supplied area of memory must be unchanged until the BIO is freed. 70 71=head1 NOTES 72 73Writes to memory BIOs will always succeed if memory is available: that is 74their size can grow indefinitely. 75 76Every read from a read write memory BIO will remove the data just read with |
| 77an internal copy operation, if a BIO contains a lots of data and it is | 77an internal copy operation, if a BIO contains a lot of data and it is |
| 78read in small chunks the operation can be very slow. The use of a read only 79memory BIO avoids this problem. If the BIO must be read write then adding 80a buffering BIO to the chain will speed up the process. 81 82=head1 BUGS 83 84There should be an option to set the maximum size of a memory BIO. 85 --- 30 unchanged lines hidden --- | 78read in small chunks the operation can be very slow. The use of a read only 79memory BIO avoids this problem. If the BIO must be read write then adding 80a buffering BIO to the chain will speed up the process. 81 82=head1 BUGS 83 84There should be an option to set the maximum size of a memory BIO. 85 --- 30 unchanged lines hidden --- |