Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Question regarding passing CURL_SOCKET_TIMEOUT to multi_socket_action
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_lists.haxx.se>
Date: Sun, 24 Oct 2021 21:40:35 +0200 (CEST)
On Sun, 24 Oct 2021, Yongkang Huang wrote:
> For 1), will the CURLMOPT_TIMERFUNCTION callback called in this case?
The CURLMOPT_TIMERFUNCTION callback is called when the timeout needs updating.
If the number of transfers is zero, that should mean that there's no timeout
left.
> For 2), that make a lot of sense, I know there¢s some code indicating added
> easy handle error like CURLM_BAD_EASY_HANDLE, in this case how to know which
> easy handle is bad so we can remove from the multi without terminate other
> good handles?
I don't think curl_multi_socket_action can return CURLM_BAD_EASY_HANDLE
without something is seriously messed up.
> Also for curl_multi_socket_action, which error would indicate the multi
> handle is corrupted and we need to clear all the added easy handle?
None? The multi handle cannot get "corrupted" without something having run
berserk and if something has, then curl cannot detect it anyway.
Date: Sun, 24 Oct 2021 21:40:35 +0200 (CEST)
On Sun, 24 Oct 2021, Yongkang Huang wrote:
> For 1), will the CURLMOPT_TIMERFUNCTION callback called in this case?
The CURLMOPT_TIMERFUNCTION callback is called when the timeout needs updating.
If the number of transfers is zero, that should mean that there's no timeout
left.
> For 2), that make a lot of sense, I know there¢s some code indicating added
> easy handle error like CURLM_BAD_EASY_HANDLE, in this case how to know which
> easy handle is bad so we can remove from the multi without terminate other
> good handles?
I don't think curl_multi_socket_action can return CURLM_BAD_EASY_HANDLE
without something is seriously messed up.
> Also for curl_multi_socket_action, which error would indicate the multi
> handle is corrupted and we need to clear all the added easy handle?
None? The multi handle cannot get "corrupted" without something having run
berserk and if something has, then curl cannot detect it anyway.
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2021-10-24