Creating and Configuring Virtual Players (CLI)
75
Media Flow Controller Administrator’s Guide
Media Flow Controller Configuration Tasks (CLI)
players. Whereas namespaces allow you to define what gets fetched from where and how,
virtual players let you fine-tune video delivery.
There are five types of virtual players: Type generic virtual player offers all generic virtual
player options; Type break players are a sub-set of Type generic, Type qss-streamlet virtual
players allow multiple settings of assured flow via a rate-map, Type yahoo players are for
YouTube™ videos and include a health-probe option and a special authentication option.
Type smoothflow players for SmoothFlow are documented after this section. Type youtube
players are for YouTube media. A sixth player type, smoothstream-pub is not supported in
Release 2.0.4.
•
“Using query-string-parm” on page 75
•
“Using hash-verify” on page 76
•
“Using virtual-player type qss-streamlet rate-map” on page 76
•
“Using Virtual Player Type youtube” on page 77
•
“Example: Configuring generic Virtual Player (CLI)” on page 78
•
“Configuring YouTube Video Caching (CLI)” on page 199
Note!
Media Flow Controller provides an API you can use to create custom virtual players. For
more information, contact Juniper Networks Customer Support; see
“Requesting
Technical Support” on page 34
.
Note!
In Release 2.0.4, the show options command ? (question mark), lists all virtual player
options no matter what virtual player type you are configuring; however, if you try to set an
option that does not apply to that player type, an error is displayed.
Using query-string-parm
The query-string-parm argument, used extensively in virtual player configurations, allows
you to use query params. Query params, a string with an associated value, are a way of
passing information through a URL. The query param part of the URL is designated with a
question mark (?) followed by defined query params. The query param is a name that is
associated with a pre-defined value. Additional queries in the URL are separated by
ampersand signs (&). Query params are composed of a name and value pair. For example, a
request for a query param for assured-flow-rate could be shown in a URL like this:
http://xyz.com/test.flv?afr=100
In the example, the query-string-parm <string> is afr and its value is 100. The namespace
for this connection tells Media Flow Controller that when it finds afr in the query params part of
the URL it is to use the value following it for that function. So, if the URL has ?afr=100 Media
Flow Controller knows (through the URL’s defined namespace and associated virtual player or
configured network connection properties) to use 100 Kbps for the assured-flow rate.
In the Media Flow Controller CLI, you can only specify the query param <string> and should
know the units of the value for that query parameter as query params can be defined to mean
many different things and are used to signal the start or value of assured flow, fast-start, full-
download, seek, and smooth flow functions, and the match value for hash-verify and rate-
map.
Important!
The virtual player query-string-parm values you configure in your Media Flow
Controller origin must match the corresponding query-string-parm values configured in your
Media Flow Controller edge.
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...
