Home
last modified time | relevance | path

Searched refs:multi_socket (Results 1 – 7 of 7) sorted by relevance

/curl/tests/data/
H A Dtest53037 multi_socket interface transfer with callbacks returning error
/curl/tests/
H A Dvalgrind.supp73 fun:multi_socket
/curl/docs/libcurl/
H A Dcurl_multi_timeout.md44 An application that uses the *multi_socket* API should not use this function.
H A Dlibcurl-multi.md59 the event based one we call multi_socket. You benefit from reading through the
141 The multi_socket API is designed to inform your application about which
H A Dlibcurl-tutorial.md1359 interface. The event based one, also called multi_socket and the "normal one"
1361 on the multi_socket event based API, this description here is for the select()
/curl/lib/
H A Dmulti.c3524 static CURLMcode multi_socket(struct Curl_multi *multi, function
3710 return multi_socket(multi, FALSE, s, 0, running_handles);
3719 return multi_socket(multi, FALSE, s, ev_bitmask, running_handles);
3727 return multi_socket(multi, TRUE, CURL_SOCKET_BAD, 0, running_handles);
/curl/docs/
H A DTODO513 The multi_socket API should work with edge-triggered socket events. One of

Completed in 26 milliseconds