3.1.4.2.2 Sending a LinkViewerToMacStartStriding Message

The client MUST fill in the fields of the LinkViewerToMacStartStriding (section 2.2.4.26) message.

The value of the openFileId field in the LinkViewerToMacStartStriding (section 2.2.4.26) message MUST be set to the value of the File-ID variable in the abstract data model.

Depending on how the higher layer has specified the position from which the server is supposed to start streaming, the client MUST assign the start position to the position field, the asfOffset field, or the locationId field.

If the higher layer wants only a portion of the content to be streamed, the stop position SHOULD be assigned to the frameOffset field.

The value of the playIncarnation field in the LinkViewerToMacStartStriding (section 2.2.4.26) message MUST be set to the value of the PlayIncarnation variable in the abstract data model. The value of the PlayIncarnation variable MUST then be incremented.<32>

The client MUST set the value of the PlayIncarnation-For-Stop variable to the value that is assigned to the playIncarnation field in the LinkViewerToMacStartStriding (section 2.2.4.26) message.

The higher layer MUST specify at what rate the multimedia content is played back. For example, if the higher layer wants to play the multimedia content in reverse, it MUST specify this and the rate of playback. The client MUST set the rate field in the LinkViewerToMacStartStriding (section 2.2.4.26) message to that rate.

The message MUST be sent following the rules specified in section 3.1.5.1.

The client MUST set the value of the Striding-Sent variable to 1.

After sending the LinkViewerToMacStartStriding (section 2.2.4.26) message, if the value of the Stream-Switch-Sent variable is 1, then the client MUST wait for a LinkMacToViewerReportStreamSwitch (section 2.2.4.13) message to be received. How to process the LinkMacToViewerReportStreamSwitch (section 2.2.4.13) message is specified in section 3.1.5.14.

Otherwise, the client MUST wait for the LinkMacToViewerReportStartStriding (section 2.2.4.11) message to be received. How to process this message is specified in section 3.1.5.16.

Show: