summaryrefslogtreecommitdiff
path: root/CHANGES
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2005-06-02 11:58:04 +0000
committerDaniel Stenberg <daniel@haxx.se>2005-06-02 11:58:04 +0000
commit4e9c5b2dbb6b30b2662a70d9756d717d63475df8 (patch)
tree1557100c90922cff0a4ab212a4c13d97bbef357e /CHANGES
parentae75ee14234b6d1b22832081d7dbd1d281c955cb (diff)
downloadc-ares-4e9c5b2dbb6b30b2662a70d9756d717d63475df8.tar.gz
c-ares-4e9c5b2dbb6b30b2662a70d9756d717d63475df8.tar.bz2
c-ares-4e9c5b2dbb6b30b2662a70d9756d717d63475df8.zip
William Ahern:
Make UDP sockets non-blocking. I've confirmed that at least on Linux 2.4 a read event can come back from poll() on a valid SOCK_DGRAM socket but recv(2) will still block. This patch doesn't ignore EAGAIN in read_udp_packets(), though maybe it should. (This patch was edited by Daniel Stenberg and a new configure test was added (imported from curl's configure) to properly detect what non-blocking socket approach to use.)
Diffstat (limited to 'CHANGES')
-rw-r--r--CHANGES7
1 files changed, 7 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index cb1fdac..678319d 100644
--- a/CHANGES
+++ b/CHANGES
@@ -4,6 +4,13 @@
- William Ahern:
+ Make UDP sockets non-blocking. I've confirmed that at least on Linux 2.4 a
+ read event can come back from poll() on a valid SOCK_DGRAM socket but
+ recv(2) will still block. This patch doesn't ignore EAGAIN in
+ read_udp_packets(), though maybe it should. (This patch was edited by Daniel
+ Stenberg and a new configure test was added (imported from curl's configure)
+ to properly detect what non-blocking socket approach to use.)
+
I'm not quite sure how this was happening, but I've been seeing PTR queries
which seem to return empty responses. At least, they were empty when calling
ares_expand_name() on the record. Here's a patch which guarantees to