Media Flow Controller Overview : Media Flow Controller Functions : Namespace

Namespace
The namespace feature allows you to classify different types of traffic based on a combination of URL and FQDN, and apply separate delivery policies to each type of classified traffic. This gives you a way to separate your video delivery traffic characteristics based on any given variable in the stream/request being received by Media Flow Controller from the client.
At a minimum, namespace configuration requires a domain (only one per namespace), an origin-server (one per namespace unless using server-map), and a match criteria (to refine delivery of incoming requests). Additional parameters for origin-fetch, cache options, and so forth, are optional. You can also further define control by assigning a configured virtual-player (overrides network connection global defaults). The namespace is referenced via the URL in the HTTP request directed to Media Flow Controller. For example; if you are serving content through Media Flow Controller for media under the following directories from your origin library...
... you might create three namespaces: TRG, UGC, and Premium each with a different set of delivery policies. For example, requests with a domain FQDN example.com and match uri of /video/premium would be processed according to the delivery policies (uri-prefix, protocol, domain, origin-server, virtual-player, and so on) defined in the namespace example as shown below (output of show namespace example):
Namespace: example
Active: yes
Precedence: 0
cluster-Hash: Complete url
Domain Name: example.com
Proxy Mode: reverse
Match Type:
URI-Prefix - /video/premium
Origin-Server: nfs://example.com:/vod/premium/
Delivery Protocol: http Status Enabled: yes
Origin Fetch Configuration:
Cache-Age (Default): 28800 (seconds)
Cache Age Threshold: 60 (seconds)
Cache-Directive: follow
Object Size Threshold: NONE (Always Cached)
Modify Date Header: deny
Origin Request Configuration:
Cache-Revalidate: permit
Use 'Date' Header when Last-Modified is not present: no
Convert HEAD to GET: permit
Host-header Inherit: permit
Set X-Forwaded-For Header : yes
Client-Request Configuration:
Allow objects with a query-string to be cached: no
Cache control max age: 0
Cache control max age action: serve-from-origin
Client-Response Configuration :
Delivery Protocol: rtsp Status Enabled: no
Origin Fetch Configuration:
Cache-Age (Default): 28800 (seconds)
Cache Age Threshold: 60 (seconds)
Cache-Directive: follow
Object Size Threshold: NONE (Always Cached)
Virtual Player: sfplayer
Live Pub-Point Details:
Pre-stage FTP Configuration:
User: example_ftpuser

Report an Error
Media Flow Controller Administrator's Guide and CLI Command Reference
Copyright © 2010 Juniper Networks, Inc.