This topic discusses a type of behavior that a cache/proxy plug-in could provide when used with Windows Media Services. The cache/proxy plug-in you obtain or create may behave differently.
After a cache/proxy plug-in is installed on a Windows Media
server it can provide support for caching on-demand content from
another Windows Media server. When a client requests on-demand
content, the cache/proxy plug-in verifies that the content is
cached locally and is current. To do this, the plug-in first checks
the cache expiration property of the content. If the content is set
to expire after a certain time that has already passed, the plug-in
then requests that the
If a cache hit occurs, the plug-in requests that the cache/proxy server stream the content from its cache to the client.
If a cache miss occurs, the content is purged from the cache, and the cache/proxy server downloads the updated content from the origin server. The cache/proxy server initiates another connection to the origin server to act as a proxy server to deliver the content to the client.
If a cache miss occurs when the cache/proxy server attempts to
stream multiple-bit-rate (MBR) content, the
cache/proxy server will attempt to download all of the different
bit rate streams from the origin server at once. If you have set a
If content was moved to a different location on the origin server, the cache/proxy plug-in can transfer client requests to the new location. For example, if the cache/proxy plug-in receives an HTTP code 301 or 302 when checking whether content is current, the plug-in updates its internal database to recognize requests for the new location.