aboutsummaryrefslogtreecommitdiff
path: root/docs/libcurl/curl_multi_timeout.3
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2008-08-06 21:22:07 +0000
committerDaniel Stenberg <daniel@haxx.se>2008-08-06 21:22:07 +0000
commita3045b4e4944a36f467f363607d6c6a50727fca2 (patch)
tree8573cef2a4fb2a005efe6d6c19a4a69bf67bffc4 /docs/libcurl/curl_multi_timeout.3
parentb0685b357607772084b05eab988fea0b6d319fc9 (diff)
- mention curl_multi_socket_action() rather than the deprecated
curl_multi_socket() - don't claim that it has an argument named 'easy' because it doesn't!
Diffstat (limited to 'docs/libcurl/curl_multi_timeout.3')
-rw-r--r--docs/libcurl/curl_multi_timeout.37
1 files changed, 3 insertions, 4 deletions
diff --git a/docs/libcurl/curl_multi_timeout.3 b/docs/libcurl/curl_multi_timeout.3
index 7302e0ac4..b4da9af89 100644
--- a/docs/libcurl/curl_multi_timeout.3
+++ b/docs/libcurl/curl_multi_timeout.3
@@ -14,10 +14,9 @@ An application using the libcurl multi interface should call
actions \- at most \- before proceeding.
Proceeding means either doing the socket-style timeout action: call the
-\fBcurl_multi_socket(3)\fP function with the \fBsockfd\fP argument set to
-CURL_SOCKET_TIMEOUT and the \fBeasy\fP argument set to CURL_EASY_TIMEOUT, or
-simply calling \fBcurl_multi_perform(3)\fP if you're using the simpler and
-older multi interface approach.
+\fBcurl_multi_socket_action(3)\fP function with the \fBsockfd\fP argument set
+to CURL_SOCKET_TIMEOUT, or call \fBcurl_multi_perform(3)\fP if you're using
+the simpler and older multi interface approach.
The timeout value returned in the long \fBtimeout\fP points to, is in number
of milliseconds at this very moment. If 0, it means you should proceed