the flushed buffer, which is not necessarily the same as after the data you've
really read.
+Most fastbuf back-ends also participate in the libucw resource management system.
+If you have a resource pool active, newly created fastbufs are automatically tied
+to resources in the pool, so when the pool gets cleaned up, the fastbufs are
+freed, too. The bclose() function is still available and it removes the tie
+as needed.
+
.Back-ends:
- <<fbparam,Files (parametrized)>>
- <<fbfile,Regular files>>