Hi. I've briefly looked at the code but I didn't directly find what I was looking for.
I'm wondering if uv_tcp_t tries to write to the socket before it decides to queue the data for next writable event? I do this in my use of uv_poll_t and it is very fast because I do not need to copy the data and queue it if it turns out the socket was writable at the very function call. So if I have a char *data I can directly write it to the kernel buffer and skip the queueing. Is this empoyed in uv_tcp_t, or do you have any opposition to this technique? -- 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.
