Has anyone run into trouble with a blocking read? I woke up this morning to
find a test server blocked on a recv(2) call. The _only_ recv(2) I can find
in my code is from Ares, and I now realize that Ares doesn't set any of it's
sockets non-blocking.
Can anyone think of any issues that might arise if I made the sockets
non-blocking and dealt with errno=EAGAIN/EWOULDBLOCK in read_udp_packets()
and read_tcp_packets()? I can't think of any off-hand.
- Bill
_______________________________________________
http://cool.haxx.se/mailman/listinfo/c-ares
Received on Tue May 17 19:19:41 2005