On 7/9/2014 12:40 AM, Saúl Ibarra Corretgé wrote:
On 7/8/2014 1:19 PM, Saúl Ibarra Corretgé wrote:
Can you try this patch?
https://gist.github.com/saghul/a2da3e48433006669c43
The artificial ENOTCONN error went away, but data written by the
client is not received - the read callback is never called.
Doh. I don't use uv_tcp_open like this, and it wasn't really intended
to be used that way... you'll have to dig inside libuv to figure it
out, sorry!
Well IMHO a tcp handle should behave consistent across platforms,
regardless of how it was constructed.
Related question - as a workaround, is it possible to register an
external fd/socket with libuv twice? Once with uv_tcp_open and again as
a poll handle (for read notifications)?
Thanks
--
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.
