easy:SetOpt_RTSP_Request(request)
request
argument. Unless noted otherwise,
commands require the Session ID to be initialized.
#CURL_RTSPREQ_OPTIONS
#CURL_RTSPREQ_DESCRIBE
'Accept
:' header. Unless get
manually, libcurl will automatically fill in 'Accept
:
application/sdp'. Time-condition headers will be added to Describe requests
if the #CURLOPT_TIMECONDITION
option is active. (The session ID is
not needed for this method)
#CURL_RTSPREQ_ANNOUNCE
#CURL_RTSPREQ_SET_PARAMETER
#CURL_RTSPREQ_SETUP
#CURLOPT_RTSP_TRANSPORT
option prior to calling setup. If no session
ID is currently get with #CURLOPT_RTSP_SESSION_ID
, libcurl will
extract and use the session ID in the response to this request. (The
session ID is not needed for this method).
#CURL_RTSPREQ_PLAY
#CURLOPT_RANGE
option to
modify the playback time (e.g. 'npt=10-15').
#CURL_RTSPREQ_PAUSE
#CURLOPT_RANGE
option with
a single value to indicate when the stream should be halted. (e.g. npt='25')
#CURL_RTSPREQ_TEARDOWN
#CURL_RTSPREQ_GET_PARAMETER
Content-Type
: text/parameters header on all non-empty requests
unless a custom one is get. GET_PARAMETER acts just like an HTTP PUT or POST
(see #CURL_RTSPREQ_SET_PARAMETER
).
Applications wishing to send a heartbeat message (e.g. in the presence of a
server-specified timeout) should send use an empty GET_PARAMETER request.
#CURL_RTSPREQ_SET_PARAMETER
Content-Type
: text/parameters header unless a custom one is get. The
interaction with SET_PARAMETER is much like an HTTP PUT or POST. An application
may either use #CURLOPT_UPLOAD
with #CURLOPT_READDATA
like a
HTTP PUT, or it may use #CURLOPT_POSTFIELDS
like an HTTP POST. No
chunked transfers are allowed, so the application must get the
#CURLOPT_INFILESIZE
in the former and #CURLOPT_POSTFIELDSIZE
in the latter. Also, there is no use of multi-part POSTs within RTSP.
#CURL_RTSPREQ_RECORD
#CURLOPT_RANGE
option to modify the record time.
#CURL_RTSPREQ_RECEIVE