Specifications

B-10
Cisco Internet Streamer CDS 2.0-2.3 Software Configuration Guide
OL-13493-04
Appendix B Creating Manifest Files
Working with Manifest Files
<playServer name="wmt">
<extension name="wmv" />
<extension name="wma" />
<extension name="wmx" />
<extension name="asf" />
</playServer>
<playServer name="http">
<contentType name="application/pdf" />
<contentType name="application/postscript" />
<extension name="pdf" />
<extension name="ps" />
</playServer>
</playServerTable>
The <playServerTable> tag is used to generate a playserver list for each content type. In the preceding
example, any Portable Document Format (.pdf) or PostScript (.ps) file uses HTTP to play the content.
Customized Manifest Playserver Tables and the HTTP Playserver
In general, you do not need to specify your own playserver table or playserver in the Manifest file. A
default playserver table maps appropriate file extensions or MIME-types to the proper playservers
When you use the default playserver table, the HTTP playserver is always included in the playserver list,
and this allows prefetched content to be played using HTTP. If the default playserver table does not meet
your needs, you can customize your playserver lists by defining your own playserver table or by
specifying a playServer attribute in the Manifest file.
The HTTP playserver is included in the default playserver table. However, if you specify your own
playserver table or playServer attribute in the <item> or <crawler> tags, you must add the HTTP
playserver in order to play HTTP content or other content using HTTP.
Specifying Attributes for Content Serving
Certain attributes in the Manifest file can be specified to control the manner in which content is served
by the Service Engines. These attributes can be specified in the <item> and <crawler> tags. These same
attributes can also be specified in the <item-group> or <options> tags, so they can be shared by their
<item> and <crawler> subtags. Table B-3 lists and describes these content-serving attributes.
Table B-3 Attributes for Content Serving
Attribute Description
serveStartTime (Optional) Designates a time in yyyy-mm-dd hh:mm:ss format at which the
CDS software is allowed to start serving the content. If the serving start time
is omitted, content is ready to serve once it is distributed to the Service Engine.
serveStopTime (Optional) Designates a time in yyyy-mm-dd hh:mm:ss format at which the
CDS software temporarily stops serving the content. If the serving stop time
is omitted, the CDS software serves the content to the Service Engine until the
content is removed by modifying the Manifest file or renaming the delivery
service.