diff options
Diffstat (limited to 'docs/libcurl/libcurl-multi.3')
| -rw-r--r-- | docs/libcurl/libcurl-multi.3 | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/libcurl/libcurl-multi.3 b/docs/libcurl/libcurl-multi.3 index aa408242e..bafeb0a0a 100644 --- a/docs/libcurl/libcurl-multi.3 +++ b/docs/libcurl/libcurl-multi.3 @@ -32,7 +32,7 @@ for an overview of the libcurl easy interface. All functions in the multi interface are prefixed with curl_multi. .SH "OBJECTIVES" -The multi interface offers several abilities that the easy interface doesn't. +The multi interface offers several abilities that the easy interface does not. They are mainly: 1. Enable a "pull" interface. The application that uses libcurl decides where @@ -77,8 +77,8 @@ Adding the easy handle to the multi handle does not start the transfer. Remember that one of the main ideas with this interface is to let your application drive. You drive the transfers by invoking \fIcurl_multi_perform(3)\fP. libcurl will then transfer data if there is -anything available to transfer. It'll use the callbacks and everything else -you have setup in the individual easy handles. It'll transfer data on all +anything available to transfer. it will use the callbacks and everything else +you have setup in the individual easy handles. it will transfer data on all current transfers in the multi stack that are ready to transfer anything. It may be all, it may be none. When there's nothing more to do for now, it returns back to the calling application. @@ -157,11 +157,11 @@ libevent, libev, kqueue, epoll or similar) with which the application better scale upward and beyond thousands of simultaneous transfers without losing performance. -When you've added your initial set of handles, you call +When you have added your initial set of handles, you call \fIcurl_multi_socket_action(3)\fP with CURL_SOCKET_TIMEOUT set in the sockfd -argument, and you'll get callbacks call that sets you up and you then continue +argument, and you will get callbacks call that sets you up and you then continue to call \fIcurl_multi_socket_action(3)\fP accordingly when you get activity on -the sockets you've been asked to wait on, or if the timeout timer expires. +the sockets you have been asked to wait on, or if the timeout timer expires. You can poll \fIcurl_multi_info_read(3)\fP to see if any transfer has completed, as it then has a message saying so. |