From 632b3d81d6501108c13dd25f4d412e7e28ab3ad3 Mon Sep 17 00:00:00 2001 From: Clemens Gruber Date: Sun, 8 Sep 2013 19:01:26 +0200 Subject: curl_easy_pause: suggest one way to unpause --- docs/libcurl/curl_easy_pause.3 | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'docs/libcurl/curl_easy_pause.3') diff --git a/docs/libcurl/curl_easy_pause.3 b/docs/libcurl/curl_easy_pause.3 index 7debfd842..402bb0546 100644 --- a/docs/libcurl/curl_easy_pause.3 +++ b/docs/libcurl/curl_easy_pause.3 @@ -38,8 +38,11 @@ that returns pause signals to the library that it couldn't take care of any data at all, and that data will then be delivered again to the callback when the writing is later unpaused. -NOTE: while it may feel tempting, take care and notice that you cannot call -this function from another thread. +While it may feel tempting, take care and notice that you cannot call this +function from another thread. To unpause, you may for example call it from the +progress callback (see \fIcurl_easy_setopt(3)\fP's +\fICURLOPT_PROGRESSFUNCTION\fP), which gets called at least once per second, +even if the connection is paused. When this function is called to unpause reading, the chance is high that you will get your write callback called before this function returns. -- cgit v1.2.3