From 465ae39e86396c2d1a84735164964a43a9c157e1 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 4 Mar 2002 10:10:58 +0000 Subject: moved to the new libcurl/ directory --- docs/curl_multi_perform.3 | 30 ------------------------------ 1 file changed, 30 deletions(-) delete mode 100644 docs/curl_multi_perform.3 (limited to 'docs/curl_multi_perform.3') diff --git a/docs/curl_multi_perform.3 b/docs/curl_multi_perform.3 deleted file mode 100644 index dae41ace8..000000000 --- a/docs/curl_multi_perform.3 +++ /dev/null @@ -1,30 +0,0 @@ -.\" $Id$ -.\" -.TH curl_multi_perform 3 "1 March 2002" "libcurl 7.9.5" "libcurl Manual" -.SH NAME -curl_multi_perform - add an easy handle to a multi session -.SH SYNOPSIS -#include - -CURLMcode curl_multi_perform(CURLM *multi_handle, int *running_handles); -.ad -.SH DESCRIPTION -When the app thinks there's data available for the multi_handle, it should -call this function to read/write whatever there is to read or write right -now. 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 -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. -.SH "RETURN VALUE" -CURLMcode type, general libcurl multi interface error code. - -NOTE that this only returns errors etc regarding the whole multi stack. There -might still have occurred problems on invidual transfers even when this -function returns OK. -.SH "TYPICAL USAGE" -Most application will use \fIcurl_multi_fdset\fP to get the multi_handle's -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\fP gets called. -.SH "SEE ALSO" -.BR curl_multi_cleanup "(3)," curl_multi_init "(3)" -- cgit v1.2.3