Streaming With Rtsp; Table 4 Rtsp Methods - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide
Table 3 HTTP Methods (Continued)
Method
OPTIONS
POST
PUT
TRACE

Streaming with RTSP

Streaming media servers can use the HTTP/TCP protocols as well as specialized protocols
such as the User Datagram Protocol (UDP). UDP does not do re-transmission or data-rate
management functionality, making it ideal for transmitting real-time audio and video data,
which can tolerate some lost packets. Streaming media servers can use an intelligent
retransmission scheme to ensure that only lost packets that can be sent to the client in time to
get played are retransmitted.
A compressed media file is produced and copied to a specialized streaming media server
instead of a Web server. Data is sent to the client at the exact rate associated with the
compressed audio and video streams, rather than at a set rate. The server and the client
communicate during the delivery process allowing additional services to be applied.
RTSP/RTP can dynamically respond to client feedback, adjusting delivery rates appropriately,
increasing the likelihood of uninterrupted viewing. Advanced features such as detailed
reporting of streams played, VCR controls (seek, fast-forward, rewind), live video delivery, and
delivery of multiple streams to the client are available.
Because Web server streaming typically creates a local cached copy of every media file played,
there is no way to prevent end users from keeping the media. With an RTSP/RTP delivery
scheme, users can only stream data and cannot download a media file to their hard disk.
Table 4 describes the RTSP methods supported for Media Flow Controller in Release 2.0.4.,
where C stands for Client, and S stands for server.
Table 4 RTSP Methods
Method
DESCRIBE
OPTION
PAUSE
PLAY
SETUP
TEARDOWN
Get available request/response options. Responses are not cacheable.
Request server action:
•
annotate an existing resource
•
post a message
•
accept a block of data
•
append data in a database
Responses are not cacheable without the Cache-Control or Expires header.
Request to store or create a resource.
Responses not cacheable.
Invoke a loop-back of the request, for testing or diagnosis. Not cacheable.
Direction Requirement
C --> S REQUIRED
C --> S, S --> C Recommended
C --> S Recommended
C --> S REQUIRED
C --> S REQUIRED
C --> S REQUIRED
Media Flow Controller Overview
Description
Description
Get description of media object
Get available request/response options
Halt delivery but keep state
Start playback via the transport
mechanism established with SETUP
Establish transport mechanism
Remove state
Media Flow Controller Delivery Methods 47