aboutsummaryrefslogtreecommitdiff
path: root/docs/libcurl/curl_multi_timeout.3
AgeCommit message (Collapse)Author
2010-04-12refer to CURLMOPT_TIMERFUNCTION for multi_socket usersDaniel Stenberg
curl_multi_timeout(3) is simply the wrong function to use if you're using the multi_socket API and this document now states this pretty clearly to help guiding users.
2010-03-24remove the CVSish $Id$ linesDaniel Stenberg
2008-08-06- mention curl_multi_socket_action() rather than the deprecatedDaniel Stenberg
curl_multi_socket() - don't claim that it has an argument named 'easy' because it doesn't!
2008-02-03it is stable now...Daniel Stenberg
2007-12-06clarify that when curl_multi_timeout() returns -1 it just means that thereDaniel Stenberg
is no current timeout. It does not mean wait forever and it does not mean do not wait at all. It means there is no timeout value known at this point in time.
2006-06-24corrected introduction version numberDaniel Stenberg
2006-01-03fixed the prototypeDaniel Stenberg
2006-01-02Initial description of the upcoming curl_multi_timeout() functionDaniel Stenberg