curl_multi_socket_action() is the one to use nowadays, as Mohun Biswas
pointed out!
This commit is contained in:
parent
c32cf33a16
commit
7ae624e700
@ -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
|
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).
|
again (possibly after having altered some options at your own choice).
|
||||||
.SH "MULTI_SOCKET"
|
.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
|
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
|
offers a much more high-performance API that will make a significant
|
||||||
for applications using large numbers of simultaneous connections.
|
difference for applications using large numbers of simultaneous connections.
|
||||||
|
|
||||||
\fIcurl_multi_socket_action(3)\fP is then used
|
\fIcurl_multi_socket_action(3)\fP is then used
|
||||||
instead of \fIcurl_multi_perform(3)\fP.
|
instead of \fIcurl_multi_perform(3)\fP.
|
||||||
|
Loading…
Reference in New Issue
Block a user