Unverified Commit 63b8fbbb authored by Daniel Stenberg's avatar Daniel Stenberg
Browse files

curl_multi_fdset.3: emphasize curl_multi_timeout 

... even when there's no socket to wait for, the timeout can still be
very short.
parent fa64b0fc

docs/libcurl/curl_multi_fdset.3

+5 −4
Original line number Diff line number Diff line
@@ -5,7 +5,7 @@ 
.\" *                            | (__| |_| |  _ <| |___

.\" *                             \___|\___/|_| \_\_____|

.\" *

.\" * Copyright (C) 1998 - 2014, Daniel Stenberg, <daniel@haxx.se>, et al.

.\" * Copyright (C) 1998 - 2017, Daniel Stenberg, <daniel@haxx.se>, et al.

.\" *

.\" * This software is licensed as described in the file COPYING, which

.\" * you should have received as part of this distribution. The terms
@@ -58,9 +58,10 @@ libcurl set. When libcurl returns -1 in \fImax_fd\fP, it is because libcurl 
currently does something that isn't possible for your application to monitor

with a socket and unfortunately you can then not know exactly when the current

action is completed using select(). You then need to wait a while before you

proceed and call \fIcurl_multi_perform(3)\fP anyway. How long to wait? We

suggest 100 milliseconds at least, but you may want to test it out in your own

particular conditions to find a suitable value.

proceed and call \fIcurl_multi_perform(3)\fP anyway. How long to wait? Unless

\fIcurl_multi_timeout(3)\fP gives you a lower number, we suggest 100

milliseconds or so, but you may want to test it out in your own particular

conditions to find a suitable value.



When doing select(), you should use \fIcurl_multi_timeout(3)\fP to figure out

how long to wait for action. Call \fIcurl_multi_perform(3)\fP even if no