Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

curl_multi_timeout man page: #9155

jvvprasad78 opened this issue Jul 14, 2022 · 0 comments

curl_multi_timeout man page: #9155

jvvprasad78 opened this issue Jul 14, 2022 · 0 comments


Copy link

jvvprasad78 commented Jul 14, 2022

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()

@bagder bagder self-assigned this Jul 14, 2022
bagder added a commit that referenced this issue Jul 14, 2022
Fixes #9155
Reported-by: jvvprasad78 on github
@bagder bagder closed this as completed in a88dbe4 Jul 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Successfully merging a pull request may close this issue.

2 participants