From a3045b4e4944a36f467f363607d6c6a50727fca2 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Wed, 6 Aug 2008 21:22:07 +0000 Subject: - 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! --- docs/libcurl/curl_multi_timeout.3 | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'docs/libcurl/curl_multi_timeout.3') 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 -- cgit v1.2.3