*
* If you want to use fastbufs to access files, you can choose one of several
* back-ends and set their parameters.
- *
- * All file fastbufs are tied to resources automatically.
***/
/**
*
* The `fblim` back-end reads from a file handle, but at most a given
* number of bytes. This is frequently used for reading from sockets.
- *
- * All such fastbufs are tied to resources automatically.
***/
struct fastbuf *bopen_limited_fd(int fd, uns bufsize, uns limit); /** Create a fastbuf which reads at most @limit bytes from @fd. **/
* First, you use @fbmem_create() to create the stream and the fastbuf
* used for writing to it. Then you can call @fbmem_clone_read() to get
* an arbitrary number of fastbuf for reading from the stream.
- *
- * All in-memory fastbufs are tied to resources automatically.
***/
struct fastbuf *fbmem_create(uns blocksize); /** Create stream and return its writing fastbuf. **/
* size and it is expanded to accomodate all data.
*
* At every moment, you can use `fastbuf->buffer` to gain access to the stream.
- *
- * All fastbufs of this type are tied to resources automatically.
***/
struct mempool;
*
* Please note that initialization of the clones is not thread-safe,
* so you have to serialize it yourself.
- *
- * The atomic fastbufs are tied to resources automatically.
***/
struct fb_atomic {