aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorClemens Gruber <clemensgru@gmail.com>2013-09-08 19:01:26 +0200
committerDaniel Stenberg <daniel@haxx.se>2013-09-08 19:26:28 +0200
commit632b3d81d6501108c13dd25f4d412e7e28ab3ad3 (patch)
tree844b039ea4cc7e24dff00aeff50eadf5e1867eb1
parent241aeadc50166ac2430ac6d5881d2e9a4c826440 (diff)
curl_easy_pause: suggest one way to unpause
-rw-r--r--docs/libcurl/curl_easy_pause.37
1 files changed, 5 insertions, 2 deletions
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.