aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2004-10-03 17:38:57 +0000
committerDaniel Stenberg <daniel@haxx.se>2004-10-03 17:38:57 +0000
commitf4f961c4eacdb3036bf8c4f7ba8cb959ee3d61ab (patch)
treec5e27b9b563499b963284afee81b6818d0d50598
parente2fe03df8ed10f1454888af03413f5c554095eec (diff)
added info about how users get info (like the CURLcode return code) from
individual transfers
-rw-r--r--docs/libcurl/curl_multi_perform.310
1 files changed, 9 insertions, 1 deletions
diff --git a/docs/libcurl/curl_multi_perform.3 b/docs/libcurl/curl_multi_perform.3
index 263550df2..75f72c5d8 100644
--- a/docs/libcurl/curl_multi_perform.3
+++ b/docs/libcurl/curl_multi_perform.3
@@ -16,6 +16,13 @@ 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
write the number of handles that still transfer data in the second argument's
integer-pointer.
+
+When you call curl_multi_perform() and the amount of \fIrunning_handles\fP is
+changed from the previous call (or is less than the amount of easy handles
+you've added to the multi handle), you know that there is one or more
+transfers less "running". You can then call \fIcurl_multi_info_read(3)\fP to
+get information about each individual completed transfer, and that returned
+info includes CURLcode and more.
.SH "RETURN VALUE"
CURLMcode type, general libcurl multi interface error code.
@@ -34,4 +41,5 @@ file descriptors, then it'll wait for action on them using select() and as
soon as one or more of them are ready, \fIcurl_multi_perform(3)\fP gets
called.
.SH "SEE ALSO"
-.BR curl_multi_cleanup "(3)," curl_multi_init "(3)," curl_multi_fdset "(3)"
+.BR curl_multi_cleanup "(3), " curl_multi_init "(3), "
+.BR curl_multi_fdset "(3), " curl_multi_info_read "(3)"