From: Daniel Stenberg Date: Tue, 7 Aug 2007 21:14:31 +0000 (+0000) Subject: Usage of the BCURLOPT_PROGRESSFUNCTION callback is not recommended when using X-Git-Tag: upstream/7.37.1~8828 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=c1b9356081d75c00f5907605a32e0fc3f5b8f46b;p=platform%2Fupstream%2Fcurl.git Usage of the BCURLOPT_PROGRESSFUNCTION callback is not recommended when using the multi interface, but having the comment in here caused more questions than we fixed problems so I remove it now. It still works fine. --- diff --git a/docs/libcurl/curl_easy_setopt.3 b/docs/libcurl/curl_easy_setopt.3 index 62d8aa1..fa2aa57 100644 --- a/docs/libcurl/curl_easy_setopt.3 +++ b/docs/libcurl/curl_easy_setopt.3 @@ -196,8 +196,7 @@ this callback will cause libcurl to abort the transfer and return If you transfer data with the multi interface, this function will not be called during periods of idleness unless you call the appropriate libcurl -function that performs transfers. Usage of the \fBCURLOPT_PROGRESSFUNCTION\fP -callback is not recommended when using the multi interface. +function that performs transfers. \fICURLOPT_NOPROGRESS\fP must be set to FALSE to make this function actually get called.