From 7ae624e7004338683c659fe881c1847fe9ee708a Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 15 Jun 2009 20:49:23 +0000 Subject: curl_multi_socket_action() is the one to use nowadays, as Mohun Biswas pointed out! --- docs/libcurl/libcurl-multi.3 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/libcurl/libcurl-multi.3') 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. -- cgit v1.2.3