We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Studied the code of the example programs for CURLMOPT_TIMERFUNCTION:
CURLMOPT_TIMERFUNCTION
These example programs don't handle timeout_ms == -1 correctly.
timeout_ms == -1
The documentation for CURLMOPT_TIMERFUNCTION says:
A timeout_ms value of -1 means you should delete your timer.
These example programs call curl_multi_socket_action() instead:
curl_multi_socket_action()
These exampe programs schedule a new timer instead:
Note that the timeout value 0 also has a special meaning:
A timeout_ms value of 0 means you should call curl_multi_socket_action or curl_multi_perform (once) as soon as possible.
7.52.1
All
The text was updated successfully, but these errors were encountered:
The good thing is that just having an extra timer running or calling curl_multi_socket_action() an extra time are all pretty harmless actions.
Sorry, something went wrong.
multi-uv.c seems to handle it already.
I've fixed asiohiper.cpp and evhiperfifo.c in commit d6bb1f1
asiohiper.cpp / evhiperfifo.c: deal with negative timerfunction input
d6bb1f1
That means delete the timer. Reported-by: Michael Kaufmann Ref: #1253
e5491e0
Thanks!
No branches or pull requests
I did this
Studied the code of the example programs for
CURLMOPT_TIMERFUNCTION
:These example programs don't handle
timeout_ms == -1
correctly.I expected the following
The documentation for
CURLMOPT_TIMERFUNCTION
says:These example programs call
curl_multi_socket_action()
instead:These exampe programs schedule a new timer instead:
Note that the timeout value 0 also has a special meaning:
curl/libcurl version
7.52.1
operating system
All
The text was updated successfully, but these errors were encountered: