Well, it may be useful for some applications like `bud` or node.js TLS implementation.
We have a ring buffer consisting from a multiple sub-buffers, and it could be beneficial to read into all of them at once. On Mon, Jun 30, 2014 at 12:05 PM, Iñaki Baz Castillo <[email protected]> wrote: > 2014-06-30 10:00 GMT+02:00 Fedor Indutny <[email protected]>: > > Yes, practically, it is the same. It just removes a lot of the mess with > > alloc_cb + read_cb invocations. > > So no suggested_size anymore? That may be nice for streams since the > uv_read_cb would be called again (if rearmed) when received data is > bigger than the provided buffer. But what about UDP? > > And BTW: how is it useful to pass many uv_buf_t to uv_read()? > > > -- > Iñaki Baz Castillo > <[email protected]> > > -- > You received this message because you are subscribed to the Google Groups > "libuv" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/libuv. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
