confill requirements

About the confill command

You can use the confill command to download origin server files into the cache. The confill command downloads a streaming media file and caches it to disk so all clients can access it. You can use HTTP or FTP to download the source file. The following sections describe the use of the confill command. For a syntax description of the confill command, see Prefilling streaming media content.

Streaming media types supported by confill

You can use the confill command to pull the following types of streaming media content into the cache:

Windows Media
RealSystem
QuickTime

QuickTime confill requirements

Consider the following when using the confill command to pull QuickTime files into the cache:

You can prefill only QuickTime audio and video tracks.
You cannot use the confill command to prefill QuickTime files that contain data in external files. All meta data and payload data must be present in the file that is to be pulled.
For optimal performance, hint QuickTime streams using a "optimize for server" option. In the QuickTime Player, the option is called Optimize Hints for Server. In typical applications, this type of hinting improves confill performance.

confill requirements for acceleration deployments

If you are using the confill method to prefill content, you must use the URL of the origin server as the target URL of the confill command. Otherwise, your clients cannot access the prefilled content. The reason for this is that content must be cached under the URL of the origin server so that cache misses can be resolved from the origin server.

For example, the following acceleration rule correctly directs the streaming accelerator to search for content that includes the URL of the origin server:

accelerator-ip 1755 * origin-server-ip 1755 *

Given the preceding rule, if you prefill (cache) content using the IP address of the streaming accelerator, clients will not be able to access content. For example, consider content that is prefilled as follows:

rtsp://accelerator-ip/foo.rm

Because the acceleration mapping rules direct the appliance to look for content cached under the IP address of the origin server, your prefilled content will never be found.