You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An application that uses the multi_socket API SHOULD NOT use this function, but SHOULD instead use curl_multi_setopt and its CURLMOPT_TIMERFUNCTION option for proper and desired behavior.
Call curl_multi_timeout, then wait for action on the sockets. You figure out which sockets to wait for by calling curl_multi_fdset or by a previous call to curl_multi_socket.
So first statement tells application that is using multi_socket should avoid curl_multi_timeout, but second statement speaks about previous call to curl_multi_socket()
The text was updated successfully, but these errors were encountered:
I see following contradicting statements,
An application that uses the multi_socket API SHOULD NOT use this function, but SHOULD instead use curl_multi_setopt and its CURLMOPT_TIMERFUNCTION option for proper and desired behavior.
Call curl_multi_timeout, then wait for action on the sockets. You figure out which sockets to wait for by calling curl_multi_fdset or by a previous call to curl_multi_socket.
So first statement tells application that is using multi_socket should avoid curl_multi_timeout, but second statement speaks about previous call to curl_multi_socket()
The text was updated successfully, but these errors were encountered: