aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2009-06-15 20:49:23 +0000
committerDaniel Stenberg <daniel@haxx.se>2009-06-15 20:49:23 +0000
commit7ae624e7004338683c659fe881c1847fe9ee708a (patch)
treeb159742ed11157c7ee53607660c1a72a11fd05e3 /docs
parentc32cf33a16d31eeff9a66a1e73ce58b6791dd54d (diff)
curl_multi_socket_action() is the one to use nowadays, as Mohun Biswas
pointed out!
Diffstat (limited to 'docs')
-rw-r--r--docs/libcurl/libcurl-multi.36
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/libcurl/libcurl-multi.3 b/docs/libcurl/libcurl-multi.3
index af2198498..17041f576 100644
--- a/docs/libcurl/libcurl-multi.3
+++ b/docs/libcurl/libcurl-multi.3
@@ -119,10 +119,10 @@ If you want to re-use an easy handle that was added to the multi handle for
transfer, you must first remove it from the multi stack and then re-add it
again (possibly after having altered some options at your own choice).
.SH "MULTI_SOCKET"
-Since 7.16.0, the \fIcurl_multi_socket(3)\fP function offers a way for
+Since 7.16.0, the \fIcurl_multi_socket_action(3)\fP function offers a way for
applications to not only avoid being forced to use select(), but it also
-offers a much more high-performance API that will make a significant difference
-for applications using large numbers of simultaneous connections.
+offers a much more high-performance API that will make a significant
+difference for applications using large numbers of simultaneous connections.
\fIcurl_multi_socket_action(3)\fP is then used
instead of \fIcurl_multi_perform(3)\fP.