Creating a Namespace and Setting Namespace Options (CLI)
87
Media Flow Controller Administrator’s Guide
Media Flow Controller Configuration Tasks (CLI)
Using namespace for Live Streaming Delivery With Caching
An example namespace configuration to deliver live streaming objects with caching is given;
the delivery protocol and live-pub-point commands both enter you to prefix mode.
namespace <name>
match uri <uri-prefix>
origin-server rtsp <IP_address | hostname> [port]
status active
delivery protocol rtsp
exit
live-pub-point <pp_ name>
receive-mode on-demand
status active
caching enable
exit
exit
Using namespace for Proxy Configurations
You can use namespace settings to configure Media Flow Controller to operate as a proxy in
various ways.
•
Reverse Proxy—Setting namespace origin-server to <FQDN> or server-map implies a
reverse proxy configuration. Media Flow Controller as an edge cache is effectively a
reverse proxy that reduces network and CPU load on an origin server by serving
previously-retrieved content, and enhances user experience by decreasing latency.
•
Mid-Tier Proxy—Setting namespace origin-server to absolute-url implies a mid-tier
proxy configuration. As a mid-tier proxy, Media Flow Controller must be explicitly
configured in the browser to intercept all requests. After Media Flow Controller receives
traffic from the client, it separates the traffic; cacheable requests are sent via Media Flow
Controller for performance enhanced delivery. Non-cacheable requests are tunnelled. See
also
“Configuring Media Flow Controller Mid-Tier Proxy (CLI)” on page 203
.
•
Transparent Proxy—Setting namespace origin-server to follow header HOST or X-
NKN or follow dest-ip (with or without the use-client-ip argument) implies a transparent
proxy configuration. A transparent proxy is one that requires no browser configuration and
is not readily visible to end-users. As a transparent proxy where origin-server access is
derived from the HOST header, the X-NKN header, or the destination IP address given in
the incoming request, explicit origin-server configuration is disallowed. Use this as an
alternate to providing a single origin server address. Be sure that delivery protocol http
allow-req is set to all (default). See also
Example: Transparent Proxy Namespace
Configuration
, after
Table 10.
Summary of Contents for MEDIA FLOW CONTROLLER 2.0.4 -
Page 6: ...Media Flow Controller Administrator s Guide VI Copyright 2010 Juniper Networks Inc...
Page 24: ...LIST OF FIGURES XXIV Copyright 2010 Juniper Networks Inc...
Page 37: ...Copyright 2010 Juniper Networks Inc 37 PART 1 Media Flow Controller Administration...
Page 38: ...Media Flow Controller Administrator s Guide 38 Copyright 2010 Juniper Networks Inc...
Page 285: ...Copyright 2010 Juniper Networks Inc 285 PART 2 Media Flow Controller Command and MIB Reference...
Page 286: ...Media Flow Controller Administrator s Guide 286 Copyright 2010 Juniper Networks Inc...
