Export (0) Print
Expand All

1.1 Glossary

The following terms are defined in [MS-GLOS]:

globally unique identifier (GUID)
little-endian
Unicode

The following terms are specific to this document:

Advanced Systems Format (ASF): The file format used by Windows Media. See [ASF].

broadcast: Live or prerecorded content that can be streamed to more than one client simultaneously. The server streams the content to all clients from the same location, and does not allow clients to seek.

content: Multimedia data. Content is always in ASF format. For example, a single ASF-format music file or a single ASF-format video file.

live: Content that is streamed while it is still being encoded by an encoder.

non-pipelined mode: Mode of operation in which requests from the client must be sent on a TCP connection separate from the one being used by the server for streamingcontent to the client.

pipelined mode: Mode of operation in which requests from the client can be sent on the same TCP connection being used by the server for streamingcontent to the client.

playlist: One or more content items that are streamed sequentially.

session: The state maintained by the server when it is streamingcontent to a client. If a server-side playlist is used, the same session is used for all content in the playlist.

stream: A sequence of ASF media objects (see [ASF] section 5.2) that can be selected individually. For example, if a movie has an English and a Spanish soundtrack, each may be encoded in the ASF file as a separate stream. The video data would also be a separate stream.

streaming: The act of transferring content from a sender to a receiver.

striding: Enables fast-forward and rewind the output of a file. Files must be indexed to take advantage of these features. An index is a series of values representing positions in the file (either presentation times, frame numbers, or SMTPE time codes) with corresponding offsets into the data section of the file for each.

MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as specified in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.

 
Show:
© 2014 Microsoft