Start off with curl_multi_socket_action instead of curl_multi_socket_all

[ThePedroo]

Hello,

I've been working on replacing curl_multi_socket_all with curl_multi_socket_action, as it is deprecated. However, when replacing it, the connection seems to simply not proceed.

Before that, a curl_multi_perform was introduced after to match curl_multi_socket_all behavior inside multi_socket function, however this introduced high CPU usage.

The source code is available in GitHub if necessary.

I appreciate all work done to make cURL.

OBS: That's not the only part that does that when replacing for _socket, however a solution to one of them should solve all of them.

[bagder]

Can you describe the situation when you are calling this function?

[ThePedroo]

There are 3 cases where they're used, where one of them I can't really understand due to the complexity of the library, but I believe all of them should fall into the same case. Those are used to initialize connections, where if you remove them, they won't proceed with the processing of it (mostly read).

[ThePedroo]

Can this have some attention? It's rather important to have more information on how to switch from *_socket_action, as specifically for it, there isn't much information about.