From fbcdc192d58ee0ffada26a7ea42feade87a81ecb Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Wed, 2 Aug 2006 09:33:32 +0000 Subject: a CURLOPT_PROGRESSFUNCTION clarification --- docs/libcurl/curl_easy_setopt.3 | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'docs/libcurl/curl_easy_setopt.3') diff --git a/docs/libcurl/curl_easy_setopt.3 b/docs/libcurl/curl_easy_setopt.3 index 6ac538a7a..6be387d11 100644 --- a/docs/libcurl/curl_easy_setopt.3 +++ b/docs/libcurl/curl_easy_setopt.3 @@ -169,11 +169,12 @@ added in 7.12.3) .IP CURLOPT_PROGRESSFUNCTION Function pointer that should match the \fIcurl_progress_callback\fP prototype found in \fI\fP. This function gets called by libcurl instead of -its internal equivalent with a frequent interval during data transfer (roughly -once per second). Unknown/unused argument values pass to the callback will be -set to zero (like if you only download data, the upload size will remain -0). Returning a non-zero value from this callback will cause libcurl to abort -the transfer and return \fICURLE_ABORTED_BY_CALLBACK\fP. +its internal equivalent with a frequent interval during operation (roughly +once per second) no matter if data is being transfered or not. Unknown/unused +argument values passed to the callback will be set to zero (like if you only +download data, the upload size will remain 0). Returning a non-zero value from +this callback will cause libcurl to abort the transfer and return +\fICURLE_ABORTED_BY_CALLBACK\fP. If you transfer data with the multi interface, this function will not be called during periods of idleness unless you call the appropriate libcurl -- cgit v1.2.3