Loading lib/README.multi_socket +12 −19 Original line number Original line Diff line number Diff line Loading @@ -12,14 +12,14 @@ Implementation of the curl_multi_socket API any other transfers. (The previous API always had to scan through all any other transfers. (The previous API always had to scan through all the existing transfers.) the existing transfers.) The idea is that curl_multi_socket() calls a given callback with information The idea is that curl_multi_socket_action() calls a given callback with about what socket to wait for what action on, and the callback only gets information about what socket to wait for what action on, and the callback called if the status of that socket has changed. only gets called if the status of that socket has changed. In the API draft from before, we have a timeout argument on a per socket In the API draft from before, we have a timeout argument on a per socket basis and we also allowed curl_multi_socket() to pass in an 'easy handle' basis and we also allowed curl_multi_socket_action() to pass in an 'easy instead of socket to allow libcurl to shortcut a lookup and work on the handle' instead of socket to allow libcurl to shortcut a lookup and work on affected easy handle right away. Both these turned out to be bad ideas. the affected easy handle right away. Both these turned out to be bad ideas. The timeout argument was removed from the socket callback since after much The timeout argument was removed from the socket callback since after much thinking I came to the conclusion that we really don't want to handle thinking I came to the conclusion that we really don't want to handle Loading Loading @@ -54,20 +54,13 @@ Implementation of the curl_multi_socket API included in the c-ares 1.3.1 release. included in the c-ares 1.3.1 release. We have done a test runs with up to 9000 connections (with a single active We have done a test runs with up to 9000 connections (with a single active one). The curl_multi_socket() invoke then takes less than 10 microseconds in one). The curl_multi_socket_action() invoke then takes less than 10 average (using the read-only-1-byte-at-a-time hack). We are now below the microseconds in average (using the read-only-1-byte-at-a-time hack). We are 60 microseconds "per socket action" goal (the extra 50 is the time libevent now below the 60 microseconds "per socket action" goal (the extra 50 is the needs). time libevent needs). Status Right Now Documentation The curl_multi_socket() API is implemented according to how it is http://curl.haxx.se/libcurl/c/curl_multi_socket_action.html documented. We deem it ready to use. http://curl.haxx.se/libcurl/c/curl_multi_socket.html http://curl.haxx.se/libcurl/c/curl_multi_timeout.html http://curl.haxx.se/libcurl/c/curl_multi_timeout.html http://curl.haxx.se/libcurl/c/curl_multi_setopt.html http://curl.haxx.se/libcurl/c/curl_multi_setopt.html What is Left for the curl_multi_socket API Real world usage! Loading
lib/README.multi_socket +12 −19 Original line number Original line Diff line number Diff line Loading @@ -12,14 +12,14 @@ Implementation of the curl_multi_socket API any other transfers. (The previous API always had to scan through all any other transfers. (The previous API always had to scan through all the existing transfers.) the existing transfers.) The idea is that curl_multi_socket() calls a given callback with information The idea is that curl_multi_socket_action() calls a given callback with about what socket to wait for what action on, and the callback only gets information about what socket to wait for what action on, and the callback called if the status of that socket has changed. only gets called if the status of that socket has changed. In the API draft from before, we have a timeout argument on a per socket In the API draft from before, we have a timeout argument on a per socket basis and we also allowed curl_multi_socket() to pass in an 'easy handle' basis and we also allowed curl_multi_socket_action() to pass in an 'easy instead of socket to allow libcurl to shortcut a lookup and work on the handle' instead of socket to allow libcurl to shortcut a lookup and work on affected easy handle right away. Both these turned out to be bad ideas. the affected easy handle right away. Both these turned out to be bad ideas. The timeout argument was removed from the socket callback since after much The timeout argument was removed from the socket callback since after much thinking I came to the conclusion that we really don't want to handle thinking I came to the conclusion that we really don't want to handle Loading Loading @@ -54,20 +54,13 @@ Implementation of the curl_multi_socket API included in the c-ares 1.3.1 release. included in the c-ares 1.3.1 release. We have done a test runs with up to 9000 connections (with a single active We have done a test runs with up to 9000 connections (with a single active one). The curl_multi_socket() invoke then takes less than 10 microseconds in one). The curl_multi_socket_action() invoke then takes less than 10 average (using the read-only-1-byte-at-a-time hack). We are now below the microseconds in average (using the read-only-1-byte-at-a-time hack). We are 60 microseconds "per socket action" goal (the extra 50 is the time libevent now below the 60 microseconds "per socket action" goal (the extra 50 is the needs). time libevent needs). Status Right Now Documentation The curl_multi_socket() API is implemented according to how it is http://curl.haxx.se/libcurl/c/curl_multi_socket_action.html documented. We deem it ready to use. http://curl.haxx.se/libcurl/c/curl_multi_socket.html http://curl.haxx.se/libcurl/c/curl_multi_timeout.html http://curl.haxx.se/libcurl/c/curl_multi_timeout.html http://curl.haxx.se/libcurl/c/curl_multi_setopt.html http://curl.haxx.se/libcurl/c/curl_multi_setopt.html What is Left for the curl_multi_socket API Real world usage!
