Using cache/proxy servers

A cache/proxy server network conserves bandwidth, decreases network-imposed latency, and offsets the load on the Windows Media server (origin server) from which the content is published. Network bandwidth is minimized because only one connection from the origin server is required to upload content to and receive information from cache/proxy servers on the network. Latency is decreased because a client can receive content from a nearby cache/proxy server more quickly than it could if it had to traverse the network or the Internet to receive content from the origin server. Additionally, the load on the origin server is offset because fewer clients are connecting directly to it. These three factors result in a better viewing experience for users and operating cost reduction. You can use Windows Media Services to configure your Windows Media server as either an origin server or as a cache/proxy server on your network.

If you choose to use the Windows Media server as an origin server, you can configure properties to specify how long content streamed from on-demand or broadcast publishing points on the origin server to cache/proxy servers is valid before it must be refreshed. Cache/Proxy properties are used to specify the frequency with which remote cache/proxy servers check for updated on-demand or broadcast content on the origin server.

You can also choose to use the Windows Media server as a cache/proxy server on the network and configure Cache/Proxy Management plug-ins to configure the Windows Media server as either a cache/proxy server or a reverse proxy server for caching and proxying on-demand or live content. The WMS Cache Proxy plug-in is included in Windows Media Services for this purpose.

When you enable the WMS Cache Proxy plug-in, you can monitor and configure additional properties for the default publishing points named Cache/Proxy On-Demand (for caching and streaming on-demand content from the origin server) and Cache/Proxy Broadcast (for proxying live content from the origin server). For more information, see Managing cache/proxy publishing points.

See Also