It's completely unspecified On Tue, Jan 1, 2019 at 8:31 PM Iñaki Baz Castillo <[email protected]> wrote:
> On Wed, 2 Jan 2019 at 02:09, Jameson Nash <[email protected]> wrote: > > Sure. libuv makes no claims about when exactly the data will be sent (if > ever), except that it will be sent at most once and will not be > re-attempted after the uv_write callback is fired. (the receiving side may > have even fewer guarantees on timing and duplication, depending on the > socket protocol connecting them) > > Thanks but, in order to be more specific: isn't needed to call > uv_run() in order to uv_pipe_t to really write data into the socket? > As per my code above it is not needed. > > -- > 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 https://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 https://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
