From 5162ba05625d941bfd1bdbc47bd25b896caa44dc Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 5 Sep 2022 15:52:28 +0200 Subject: [PATCH] curl_easy_pause.3: unpausing is as fast as possible Reported-by: ssdbest on github Fixes #9410 Closes #9430 --- docs/libcurl/curl_easy_pause.3 | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/libcurl/curl_easy_pause.3 b/docs/libcurl/curl_easy_pause.3 index f8385bb703..d602fc88e1 100644 --- a/docs/libcurl/curl_easy_pause.3 +++ b/docs/libcurl/curl_easy_pause.3 @@ -45,8 +45,11 @@ 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 (\fICURLOPT_PROGRESSFUNCTION(3)\fP). -When this function is called to unpause receiving, the chance is high that you -will get your write callback called before this function returns. +When this function is called to unpause receiving, the write callback might +get called before this function returns to deliver cached content. When +libcurl delivers such cached data to the write callback, it will be delivered +as fast as possible, which may overstep the boundary set in +\fICURLOPT_MAX_RECV_SPEED_LARGE(3)\fP etc. The \fBhandle\fP argument identifies the transfer you want to pause or unpause. -- 2.47.3