mirror of
https://github.com/moparisthebest/curl
synced 2024-12-21 23:58:49 -05:00
docs: clarify the CURLOPT_INTERLEAVE* options behavior
This commit is contained in:
parent
08dbed31d5
commit
50b208e23e
@ -22,15 +22,16 @@
|
||||
.\"
|
||||
.TH CURLOPT_INTERLEAVEDATA 3 "19 Jun 2014" "libcurl 7.37.0" "curl_easy_setopt options"
|
||||
.SH NAME
|
||||
CURLOPT_INTERLEAVEDATA \- custom pointer to RTSP interleave callback
|
||||
CURLOPT_INTERLEAVEDATA \- custom pointer passed to RTSP interleave callback
|
||||
.SH SYNOPSIS
|
||||
#include <curl/curl.h>
|
||||
|
||||
CURLcode curl_easy_setopt(CURL *handle, CURLOPT_INTERLEAVEDATA, void *pointer);
|
||||
.SH DESCRIPTION
|
||||
This is the userdata \fIpointer\fP that will be passed to
|
||||
\fICURLOPT_INTERLEAVEFUNCTION(3)\fP when interleaved RTP data is
|
||||
received.
|
||||
\fICURLOPT_INTERLEAVEFUNCTION(3)\fP when interleaved RTP data is received. If
|
||||
the interleave function callback is not set, this pointer is not used
|
||||
anywhere.
|
||||
.SH DEFAULT
|
||||
NULL
|
||||
.SH PROTOCOLS
|
||||
|
@ -54,8 +54,12 @@ connection may close. The application may use \fICURL_RTSPREQ_RECEIVE\fP to
|
||||
service RTP data when no requests are desired. If the application makes a
|
||||
request, (e.g. \fICURL_RTSPREQ_PAUSE\fP) then the response handler will
|
||||
process any pending RTP data before marking the request as finished.
|
||||
|
||||
The \fICURLOPT_WRITEDATA(3)\fP is passed in the \fIuserdata\fP argument in the
|
||||
callback.
|
||||
.SH DEFAULT
|
||||
NULL
|
||||
NULL, the interleave data is then passed to the regular write function:
|
||||
\fICURLOPT_WRITEFUNCTION(3)\fP.
|
||||
.SH PROTOCOLS
|
||||
RTSP
|
||||
.SH EXAMPLE
|
||||
@ -77,4 +81,4 @@ Added in 7.20.0
|
||||
.SH RETURN VALUE
|
||||
Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not.
|
||||
.SH "SEE ALSO"
|
||||
.BR CURLOPT_INTERLEAVEFUNCTION "(3), " CURLOPT_RTSP_REQUEST "(3), "
|
||||
.BR CURLOPT_INTERLEAVEDATA "(3), " CURLOPT_RTSP_REQUEST "(3), "
|
||||
|
Loading…
Reference in New Issue
Block a user