mirror of
https://github.com/moparisthebest/curl
synced 2024-11-16 06:25:03 -05:00
curl_multi_perform.3: extended/clarified
This commit is contained in:
parent
0f76e492ae
commit
ba569a27cc
@ -5,7 +5,7 @@
|
|||||||
.\" * | (__| |_| | _ <| |___
|
.\" * | (__| |_| | _ <| |___
|
||||||
.\" * \___|\___/|_| \_\_____|
|
.\" * \___|\___/|_| \_\_____|
|
||||||
.\" *
|
.\" *
|
||||||
.\" * Copyright (C) 1998 - 2011, Daniel Stenberg, <daniel@haxx.se>, et al.
|
.\" * Copyright (C) 1998 - 2012, Daniel Stenberg, <daniel@haxx.se>, et al.
|
||||||
.\" *
|
.\" *
|
||||||
.\" * This software is licensed as described in the file COPYING, which
|
.\" * This software is licensed as described in the file COPYING, which
|
||||||
.\" * you should have received as part of this distribution. The terms
|
.\" * you should have received as part of this distribution. The terms
|
||||||
@ -28,21 +28,24 @@ curl_multi_perform - reads/writes available data from each easy handle
|
|||||||
CURLMcode curl_multi_perform(CURLM *multi_handle, int *running_handles);
|
CURLMcode curl_multi_perform(CURLM *multi_handle, int *running_handles);
|
||||||
.ad
|
.ad
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
When the app thinks there's data available for the multi_handle, it should
|
This function handles transfers on all the added handles that need attention
|
||||||
call this function to read/write whatever there is to read or write right
|
in an non-blocking fashion.
|
||||||
now. curl_multi_perform() returns as soon as the reads/writes are done. This
|
|
||||||
|
When an application has found out there's data available for the multi_handle
|
||||||
|
or a timeout has elapsed, the application should call this function to
|
||||||
|
read/write whatever there is to read or write right now etc.
|
||||||
|
curl_multi_perform() returns as soon as the reads/writes are done. This
|
||||||
function does not require that there actually is any data available for
|
function does not require that there actually is any data available for
|
||||||
reading or that data can be written, it can be called just in case. It will
|
reading or that data can be written, it can be called just in case. It will
|
||||||
write the number of handles that still transfer data in the second argument's
|
write the number of handles that still transfer data in the second argument's
|
||||||
integer-pointer.
|
integer-pointer.
|
||||||
|
|
||||||
When you call curl_multi_perform() and the amount of \fIrunning_handles\fP is
|
If the amount of \fIrunning_handles\fP is changed from the previous call (or
|
||||||
changed from the previous call (or is less than the amount of easy handles
|
is less than the amount of easy handles you've added to the multi handle), you
|
||||||
you've added to the multi handle), you know that there is one or more
|
know that there is one or more transfers less "running". You can then call
|
||||||
transfers less "running". You can then call \fIcurl_multi_info_read(3)\fP to
|
\fIcurl_multi_info_read(3)\fP to get information about each individual
|
||||||
get information about each individual completed transfer, and that returned
|
completed transfer, and that returned info includes CURLcode and more. If an
|
||||||
info includes CURLcode and more. If an added handle fails very quickly, it may
|
added handle fails very quickly, it may never be counted as a running_handle.
|
||||||
never be counted as a running_handle.
|
|
||||||
|
|
||||||
When \fIrunning_handles\fP is set to zero (0) on the return of this function,
|
When \fIrunning_handles\fP is set to zero (0) on the return of this function,
|
||||||
there is no longer any transfers in progress.
|
there is no longer any transfers in progress.
|
||||||
@ -61,12 +64,14 @@ need to wait for \&"action" and then call this function again.
|
|||||||
|
|
||||||
This function only returns errors etc regarding the whole multi stack.
|
This function only returns errors etc regarding the whole multi stack.
|
||||||
Problems still might have occurred on individual transfers even when this
|
Problems still might have occurred on individual transfers even when this
|
||||||
function returns \fICURLM_OK\fP.
|
function returns \fICURLM_OK\fP. Use \fIcurl_multi_info_read(3)\fP to figure
|
||||||
|
out how individual transfers did.
|
||||||
.SH "TYPICAL USAGE"
|
.SH "TYPICAL USAGE"
|
||||||
Most applications will use \fIcurl_multi_fdset(3)\fP to get the multi_handle's
|
Most applications will use \fIcurl_multi_fdset(3)\fP to get the multi_handle's
|
||||||
file descriptors, then it'll wait for action on them using \fBselect(3)\fP and
|
file descriptors, and \fIcurl_multi_timeout(3)\fP to get a suitable timeout
|
||||||
as soon as one or more of them are ready, \fIcurl_multi_perform(3)\fP gets
|
period, then it'll wait for action on the file descriptors using
|
||||||
called.
|
\fBselect(3)\fP. As soon as one or more file descriptor is ready,
|
||||||
|
\fIcurl_multi_perform(3)\fP gets called.
|
||||||
.SH "SEE ALSO"
|
.SH "SEE ALSO"
|
||||||
.BR curl_multi_cleanup "(3), " curl_multi_init "(3), "
|
.BR curl_multi_cleanup "(3), " curl_multi_init "(3), "
|
||||||
.BR curl_multi_fdset "(3), " curl_multi_info_read "(3), "
|
.BR curl_multi_fdset "(3), " curl_multi_info_read "(3), "
|
||||||
|
Loading…
Reference in New Issue
Block a user