Juniper MEDIA FLOW CONTROLLER 2.0.4 -, Administrator'S Manual

Page: 46 / 400

Media Flow Controller Overview Media Flow Controller Administrator’s Guide
46 Media Flow Controller Delivery Methods Copyright © 2010, Juniper Networks, Inc.
Figure 2 Media Flow Controller Ingest and Delivery Options
Streaming with HTTP
A standard Web server streams media data with HTTP on top of TCP, which handles the data
transfers. TCP is optimized for delivering non-real-time applications such as file transfers and
tries to maximize the data transfer rate while ensuring stability and high throughput. One of the
ways TCP achieves reliable data transfer is by re-transmitting lost packets; however, it cannot
ensure that all re-transmitted packets arrive in time to be played in the media stream.
Table 3 describes the HTTP methods supported for Media Flow Controller in Release 2.0.4.
Table 3 HTTP Methods
Method Description
CONNECT Reserved for proxy use.
DELETE Request to delete a resource.
Responses not cacheable.
GET Retrieve the resource identified by the Request-URI. Responses are
cacheable.
HEAD Obtain meta-information. Identical to GET except content is not returned.
Responses are cacheable.
User
User User
Media Flow Controller
Internet
g015413
Flash media server
HTTP RTSP RTMP
HTTP HTTP
RTSP
RTMP RTMP RTSP
RTMP NFS
Media
Flow
Controller
Flash
media
server
Live
sources
Streaming
server
File server Web server
RTSP/RTP
Delivery
Ingest