2002-03-04 11:09:48 +01:00
|
|
|
.\" $Id$
|
|
|
|
.\"
|
2004-04-15 17:05:12 +02:00
|
|
|
.TH curl_multi_fdset 3 "15 Apr 2004" "libcurl 7.9.5" "libcurl Manual"
|
2002-03-04 11:09:48 +01:00
|
|
|
.SH NAME
|
2002-10-15 10:39:30 +02:00
|
|
|
curl_multi_fdset - extracts file descriptor information from a multi handle
|
2002-03-04 11:09:48 +01:00
|
|
|
.SH SYNOPSIS
|
2004-04-13 16:34:12 +02:00
|
|
|
.nf
|
2002-03-04 11:09:48 +01:00
|
|
|
#include <curl/curl.h>
|
|
|
|
|
|
|
|
CURLMcode curl_multi_fdset(CURLM *multi_handle,
|
|
|
|
fd_set *read_fd_set,
|
|
|
|
fd_set *write_fd_set,
|
|
|
|
fd_set *exc_fd_set,
|
|
|
|
int *max_fd);
|
|
|
|
.ad
|
|
|
|
.SH DESCRIPTION
|
|
|
|
This function extracts file descriptor information from a given multi_handle.
|
2004-04-13 16:31:49 +02:00
|
|
|
libcurl returns its fd_set sets. The application can use these to select()
|
2004-04-14 14:13:21 +02:00
|
|
|
on. The \fIcurl_multi_perform(3)\fI function should be called as soon as one
|
|
|
|
of them are ready to be read from or written to.
|
2002-05-03 00:34:31 +02:00
|
|
|
|
|
|
|
NOTE that once this call is made, you must not remove the sets you point to,
|
|
|
|
as libcurl will need to be able to read them. It needs them after select()
|
|
|
|
calls, to know if certain sockets are readable or writable.
|
2004-04-15 17:05:12 +02:00
|
|
|
|
|
|
|
You should also be aware that when doing select(), you should consider using a
|
|
|
|
rather small (single-digit number of seconds) timeout and call
|
|
|
|
\fIcurl_multi_perform\fP regularly - even if no activity has been seen on the
|
|
|
|
fd_sets - as otherwise libcurl-internal retries and timeouts may not work as
|
|
|
|
you'd think.
|
2002-03-04 11:09:48 +01:00
|
|
|
.SH RETURN VALUE
|
2004-03-15 12:37:37 +01:00
|
|
|
CURLMcode type, general libcurl multi interface error code. See
|
2004-04-13 16:34:12 +02:00
|
|
|
\fIlibcurl-errors(3)\fP
|
2002-03-04 11:09:48 +01:00
|
|
|
.SH "SEE ALSO"
|
|
|
|
.BR curl_multi_cleanup "(3)," curl_multi_init "(3)"
|