~ubuntu-branches/ubuntu/intrepid/curl/intrepid-security

Alternative versions of curl_multi_perform() that allows the application to pass in one of the file descriptors/sockets that have been detected to have "action" on them and let libcurl perform. This allows libcurl to not have to scan through all possible file descriptors to check for action. When the application has detected action on a socket handled by libcurl, it should call curl_multi_perform() with the sockfd argument set to the socket with the action.

These functions inform the application about updates in the socket (file descriptor) status by doing none, one or multiple calls to the curl_socket_callback given with the CURLMOPT_SOCKETFUNCTION option to <a class="emphasis" href="./curl_multi_setopt.html">curl_multi_setopt(3)</a>. They update the status with changes since the previous time this function was called.

If you want to force libcurl to (re-)check all its internal sockets and transfers instead of just a single one, you call <a class="bold" href="./curl_multi_socket_all.html">curl_multi_socket_all(3)</a> instead.

An application should call <a class="bold" href="./curl_multi_timeout.html">curl_multi_timeout(3)</a> to figure out how long it should wait for socket actions - at most - before doing the timeout action: call the <a class="bold" href="./curl_multi_socket.html">curl_multi_socket(3)</a> function with the sockfd argument set to CURL_SOCKET_TIMEOUT.

CURLMcode curl_multi_socket(CURLM * multi_handle, curl_socket_t sockfd,   int *running_handles);

CURLMcode curl_multi_socket_all(CURLM *multi_handle,   int *running_handles); <a name="DESCRIPTION"></a><h2 class="nroffsh">DESCRIPTION</h2>

Alternative versions of <a class="emphasis" href="./curl_multi_perform.html">curl_multi_perform(3)</a> that allows the application to pass in one of the file descriptors/sockets that have been detected to have "action" on them and let libcurl perform. This allows libcurl to not have to scan through all possible file descriptors to check for action. When the application has detected action on a socket handled by libcurl, it should call <a class="emphasis" href="./curl_multi_socket.html">curl_multi_socket(3)</a> with the sockfd argument set to the socket with the action.

At return, the int running_handles points to will contain the number of still running easy handles within the multi handle. When this number reaches zero, all transfers are complete/done. Note that when you call <a class="emphasis" href="./curl_multi_socket.html">curl_multi_socket(3)</a> on a specific socket and the counter decreases by one, it DOES NOT necessarily mean that this exact socket/transfer is the one that completed. Use <a class="emphasis" href="./curl_multi_info_read.html">curl_multi_info_read(3)</a> to figure out which easy handle that completed.

The curl_multi_socket functions inform the application about updates in the socket (file descriptor) status by doing none, one or multiple calls to the socket callback function set with the CURLMOPT_SOCKETFUNCTION option to <a class="emphasis" href="./curl_multi_setopt.html">curl_multi_setopt(3)</a>. They update the status with changes since the previous time this function was called.

To force libcurl to (re-)check all its internal sockets and transfers instead of just a single one, you call <a class="bold" href="./curl_multi_socket_all.html">curl_multi_socket_all(3)</a>. This is typically done as the first function call before the application has any knowledge about what sockets libcurl uses.

Applications should call <a class="bold" href="./curl_multi_timeout.html">curl_multi_timeout(3)</a> to figure out how long to wait for socket actions - at most - before doing the timeout action: call the <a class="bold" href="./curl_multi_socket.html">curl_multi_socket(3)</a> function with the sockfd argument set to CURL_SOCKET_TIMEOUT.

<a name="CALLBACK"></a><h2 class="nroffsh">CALLBACK DETAILS</h2>

The socket callback function uses a prototype like this <pre>

int curl_socket_callback(CURL *easy, /* easy handle */

  curl_socket_t s, /* socket */

  int action, /* see values below */

  void *userp); /* "private" pointer */

int curl_socket_callback(CURL *easy, /* easy handle */

  curl_socket_t s, /* socket */

  int action, /* see values below */

  void *userp, /* private callback pointer */

  void *socketp); /* private socket pointer */

The callback MUST return 0.

The action (third) argument to the callback has one of five values:

The easy argument is a pointer to the easy handle that deals with this

particular socket. Note that a single handle may work with several sockets

simultaneously.

The s argument is the actual socket value as you use it within your

system.

The action argument to the callback has one of five values:

<a name="CURLPOLLNONE"></a>CURL_POLL_NONE (0) register, not interested in readiness (yet)

<a name="CURLPOLLIN"></a>CURL_POLL_IN (1) register, interested in read readiness

<a name="CURLPOLLOUT"></a>CURL_POLL_OUT (2) register, interested in write readiness

<a name="CURLPOLLINOUT"></a>CURL_POLL_INOUT (3) register, interested in both read and write readiness

<a name="CURLPOLLREMOVE"></a>CURL_POLL_REMOVE (4) deregister

</pre>

The socketp argument is a private pointer you have previously set with

<a class="emphasis" href="./curl_multi_assign.html">curl_multi_assign(3)</a> to be associated with the s socket. If no

pointer has been set, socketp will be NULL. This argument is of course a

service to applications that want to keep certain data or structs that are

strictly associated to the given socket.

The userp argument is a private pointer you have previously set with

<a class="emphasis" href="./curl_multi_setopt.html">curl_multi_setopt(3)</a> and the CURLMOPT_SOCKETDATA option.

</pre>

<a name="RETURN"></a><h2 class="nroffsh">RETURN VALUE</h2>

CURLMcode type, general libcurl multi interface error code.

If you receive CURLM_CALL_MULTI_PERFORM, this basically means that you should call curl_multi_perform again, before you wait for more actions on libcurl's sockets. You don't have to do it immediately, but the return code means that libcurl may have more data available to return or that there may be more data to send off before it is "satisfied".

7. Wait for action on any of libcurl's sockets

8, When action happens, call curl_multi_socket() for the socket(s) that got action.

9. Go back to step 6. <a name="AVAILABILITY"></a><h2 class="nroffsh">AVAILABILITY</h2>

This function was added in libcurl 7.16.0 <a name="SEE"></a><h2 class="nroffsh">SEE ALSO</h2>

This function was added in libcurl 7.15.4, although not deemed stable yet. <a name="SEE"></a><h2 class="nroffsh">SEE ALSO</h2>

<a class="manpage" href="./curl_multi_cleanup.html">curl_multi_cleanup (3)</a> <a class="manpage" href="./curl_multi_init.html"> curl_multi_init (3)</a> <a class="manpage" href="./curl_multi_fdset.html">curl_multi_fdset (3)</a> <a class="manpage" href="./curl_multi_info_read.html"> curl_multi_info_read (3)</a>

This HTML page was made with <a href="http://daniel.haxx.se/projects/roffit/">roffit</a>.

100

</body></html>

Older »