The current implementation will always set SO_SNDBUF to
CURL_WRITE_SIZE even if the SO_SNDBUF starts out larger.
The patch doesn't do a setsockopt if SO_SNDBUF is already greater than
CURL_WRITE_SIZE.

This should help folks who have set up their computer with large send buffers.

-Costa

Attachment: dont-shrink-sndbuf.diff
Description: Binary data

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html

Reply via email to