> Before dispatching to curl_multi_socket_action, you can try a 0-byte,
> blocking send() on the socket to see if it is writable. If it returns
> WSAEWOULDBLOCK, don't bother. If it passes, carry on with telling cURL
> that
> it is writable.

Interesting - I'll give that a go. My "workaround" involved restructuring a
large amount of code, so it'll be a while before I get round to going back
and trying this.
Many thanks for your help.

Tom

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2009-10-23