How is data put in to the MIOBuffer in that API? How is that better than MIOBuffer::write and IOBufferReader::read? You can already interact with MIOBuffers without having to directly manipulate IOBuffers. However, it is significantly more performant (in most cases) to work with the IOBuffer blocks, since that avoids a copy when moving data between MIOBuffers.
MIOBuffers don't really have states like OPEN, CLOSED. On Fri, Nov 8, 2019 at 7:51 PM Walt Karas <wka...@verizonmedia.com.invalid> wrote: > Can we migrate towards a MIOBuffer interface that looks more like this > https://godbolt.org/z/Wc_e7N ? Where users of the interface would not > have > to directly manipulate IOBuffers? > > TBD is a mechanism for backpressure on the input/writing side of the > MIOBuffer when one of them or all collectively are reaching some limit on > memory use. >
