curl_multi_assign man page

From dcce39da3e6f7485dca39950dfc835563de3c3ea Mon Sep 17 00:00:00 2001 From: Kirill Volinsky Date: Mon, 25 Feb 2013 10:15:31 +0000 Subject: 1 step: libcurl static link git-svn-id: http://svn.miranda-ng.org/main/trunk@3763 1316c22d-e87f-b044-9b9b-93d7a3e3ba9c --- .../docs/libcurl/curl_multi_assign.html | 63 ++++++++++++++++++++++ 1 file changed, 63 insertions(+) create mode 100644 plugins/FTPFileYM/curl-7.29.0/docs/libcurl/curl_multi_assign.html (limited to 'plugins/FTPFileYM/curl-7.29.0/docs/libcurl/curl_multi_assign.html') diff --git a/plugins/FTPFileYM/curl-7.29.0/docs/libcurl/curl_multi_assign.html b/plugins/FTPFileYM/curl-7.29.0/docs/libcurl/curl_multi_assign.html new file mode 100644 index 0000000000..fc468076fd --- /dev/null +++ b/plugins/FTPFileYM/curl-7.29.0/docs/libcurl/curl_multi_assign.html @@ -0,0 +1,63 @@ + + +curl_multi_assign man page + + + + +

NAME

curl_multi_assign - set data to association with an internal socket

SYNOPSIS

#include <curl/curl.h> +

CURLMcode curl_multi_assign(CURLM *multi_handle, curl_socket_t sockfd, void *sockptr);

DESCRIPTION

This function assigns an association in the multi handle between the given socket and a private pointer of the application. This is (only) useful for curl_multi_socket(3) uses. +

When set, the sockptr pointer will be passed to all future socket callbacks for the specific sockfd socket. +

If the given sockfd isn't already in use by libcurl, this function will return an error. +

libcurl only keeps one single pointer associated with a socket, so calling this function several times for the same socket will make the last set pointer get used. +

The idea here being that this association (socket to private pointer) is something that just about every application that uses this API will need and then libcurl can just as well do it since it already has an internal hash table lookup for this.

RETURN VALUE

The standard CURLMcode for multi interface error codes.

TYPICAL USAGE

In a typical application you allocate a struct or at least use some kind of semi-dynamic data for each socket that we must wait for action on when using the curl_multi_socket(3) approach. +

When our socket-callback gets called by libcurl and we get to know about yet another socket to wait for, we can use curl_multi_assign(3) to point out the particular data so that when we get updates about this same socket again, we don't have to find the struct associated with this socket by ourselves.

AVAILABILITY