3.1.5.6 Receiving a LinkMacToViewerReportConnectedFunnel Message

  • Article

The client MUST perform the steps in section 3.1.5.2. Also, the client MUST verify that the LinkMacToViewerReportConnectedFunnel (section 2.2.4.3) message adheres to the syntax specified in section 2.2.4.3.

The client MUST send a LinkViewerToMacOpenFile (section 2.2.4.21) message.

The value of the playIncarnation field in the LinkViewerToMacOpenFile (section 2.2.4.21) 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.<39>

The value of the fileName field in the LinkViewerToMacOpenFile (section 2.2.4.21) message MUST be set to the path component of the URI stored in the Server-URL variable in the abstract data model. The syntax for the path is specified in [RFC3986] section 3.3.

The client MAY set the value of the tokenData field in the LinkViewerToMacOpenFile (section 2.2.4.21) message to authentication data appropriate for the authentication scheme identified by the Auth-Scheme variable in the abstract data model. For example, if the value of the Auth-Scheme variable is BASIC, the client includes the user name and password in the tokenData field formatted according to the syntax rules for Basic authentication.<40>

After sending the LinkViewerToMacOpenFile (section 2.2.4.21) message, the client MUST wait for a LinkMacToViewerReportRedirect (section 2.2.4.9) message, a LinkMacToViewerSecurityChallenge (section 2.2.4.14) message, or a LinkMacToViewerReportOpenFile (section 2.2.4.7) message to be received. How to process a LinkMacToViewerReportRedirect (section 2.2.4.9) message is specified in section 3.1.5.7; how to process a LinkMacToViewerSecurityChallenge (section 2.2.4.14) message is specified in section 3.1.5.8; and how to process a LinkMacToViewerReportOpenFile (section 2.2.4.7) message is specified in section 3.1.5.9.