Loading docs/libcurl/curl_multi_socket.3 +4 −4 Original line number Diff line number Diff line Loading @@ -27,7 +27,7 @@ application has detected action on a socket handled by libcurl, it should call socket with the action. When the events on a socket are known, they can be passed as an events bitmask \fBev_bitmask\fP by first setting \fBev_bitmask\fP to 0, and then adding using bitwise OR (|) any combination of events to be choosen from CURL_CSELECT_IN, CURL_CSELECT_OUT or CURL_CSELECT_ERR. When the chosen from CURL_CSELECT_IN, CURL_CSELECT_OUT or CURL_CSELECT_ERR. When the events on a socket are unknown, pass 0 instead, and libcurl will test the descriptor internally. Loading Loading @@ -58,7 +58,7 @@ also use the \fIcurl_multi_timeout(3)\fP function to poll the value at any given time, but for an event-based system using the callback is far better than relying on polling the timeout value. Usage of \fIcurl_multi_socket(3)\fP is depricated, whereas the function is Usage of \fIcurl_multi_socket(3)\fP is deprecated, whereas the function is equivalent to \fIcurl_multi_socket_action(3)\fP, when \fBev_bitmask\fP is set to 0. Loading Loading @@ -94,7 +94,7 @@ register, interested in write readiness .IP "CURL_POLL_INOUT (3)" register, interested in both read and write readiness .IP "CURL_POLL_REMOVE (4)" deregister unregister .RE The \fIsocketp\fP argument is a private pointer you have previously set with Loading Loading @@ -134,7 +134,7 @@ them for activity. This can be done through your application code, or by way of an external library such as libevent or glib. 7. Wait for activity on any of libcurl's sockets, use the timeout value your calback has been told callback has been told 8, When activity is detected, call curl_multi_socket_action() for the socket(s) that got action. If no activity is detected and the timeout expires, Loading Loading
docs/libcurl/curl_multi_socket.3 +4 −4 Original line number Diff line number Diff line Loading @@ -27,7 +27,7 @@ application has detected action on a socket handled by libcurl, it should call socket with the action. When the events on a socket are known, they can be passed as an events bitmask \fBev_bitmask\fP by first setting \fBev_bitmask\fP to 0, and then adding using bitwise OR (|) any combination of events to be choosen from CURL_CSELECT_IN, CURL_CSELECT_OUT or CURL_CSELECT_ERR. When the chosen from CURL_CSELECT_IN, CURL_CSELECT_OUT or CURL_CSELECT_ERR. When the events on a socket are unknown, pass 0 instead, and libcurl will test the descriptor internally. Loading Loading @@ -58,7 +58,7 @@ also use the \fIcurl_multi_timeout(3)\fP function to poll the value at any given time, but for an event-based system using the callback is far better than relying on polling the timeout value. Usage of \fIcurl_multi_socket(3)\fP is depricated, whereas the function is Usage of \fIcurl_multi_socket(3)\fP is deprecated, whereas the function is equivalent to \fIcurl_multi_socket_action(3)\fP, when \fBev_bitmask\fP is set to 0. Loading Loading @@ -94,7 +94,7 @@ register, interested in write readiness .IP "CURL_POLL_INOUT (3)" register, interested in both read and write readiness .IP "CURL_POLL_REMOVE (4)" deregister unregister .RE The \fIsocketp\fP argument is a private pointer you have previously set with Loading Loading @@ -134,7 +134,7 @@ them for activity. This can be done through your application code, or by way of an external library such as libevent or glib. 7. Wait for activity on any of libcurl's sockets, use the timeout value your calback has been told callback has been told 8, When activity is detected, call curl_multi_socket_action() for the socket(s) that got action. If no activity is detected and the timeout expires, Loading
