3.2.4.2 Notification That a New ASF File Header Is Available

This event occurs when the server is ready to transmit a new entry in a server-side playlist. As a prerequisite for this event, the higher layer MUST already have notified the server that it sent the last Data packet for the previous playlist entry, as specified in section 3.2.4.1, and the value of the State variable MUST be STREAMING.

The server MUST fill in the fields of a LinkMacToViewerReportStreamChange (section 2.2.4.12) message and then send the message by following the rules specified in section 3.2.5.2.

The higher layer MUST select the streams (2) in the new playlist entry that will be streamed. This SHOULD be done by taking the value of the dwLinkBandwidth field of the LinkViewerToMacStartPlaying message into account, if the client previously sent a LinkViewerToMacStartPlaying message with that field.<48>

The server MUST be prepared to receive a LinkViewerToMacLogging message from the client. How to process a LinkViewerToMacLogging message is specified in section 3.2.5.15.

If the value of the Client-Port variable is not 0x0000, the value of the State variable MUST be set to READY, the Idle-Timeout timer MUST be started, and the server MUST also be prepared to receive a LinkViewerToMacReadBlock message from the client. How to process a LinkViewerToMacReadBlock message is specified in section 3.2.5.8.

If the value of the Client-Port variable is 0x0000, the server MUST set the value of the Incarnation variable in the abstract data model to 0x000000FF and MUST then send the ASF file header of the new playlist entry to the client by following the rules specified in section 3.2.5.8.1. After that, the server MUST start transmitting the ASF data packets from the beginning of the new playlist entry by following the rules specified in section 3.2.5.11.1.

Show: