Service providers are using 3-tier architectures de-coupling front end servers from back-end storage servers by deploying mid-tier proxies. Mid-tier proxies reduce network latency, save bandwidth costs, offload origin servers, and scale front-end server throughput. Media requests are handled by front-end servers, supporting multiple protocols, that issue HTTP fetch requests to Media Flow Controller mid-tier proxy, instead of to origin servers. Media Flow Controller serves the content just as an origin server would in a network without mid-tier servers.
You can configure Media Flow Controller as a mid-tier proxy via a
namespace setting. In this deployment, you must also configure user browsers to point at the Media Flow Controller;
domain and
match uri-prefix settings are generally irrelevant and can be set to
any and
/ (slash), respectively. If you have multiple namespaces, set a low precedence (
10 is the lowest) so incoming requests can pass to namespaces with specific
uri-prefix matches (instead of
/ that accepts all incoming requests).