Export (0) Print
Expand All

3.1.5.5 Receiving a LinkMacToViewerReportDisconnectedFunnel Message

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

The client SHOULD close the TCP connection to the server and report the error specified in the hr field of the LinkMacToViewerReportDisconnectedFunnel (section 2.2.4.4) message to the higher layer.

Alternatively, the client MAY send a new LinkViewerToMacConnectFunnel (section 2.2.4.18) message. The following rules apply to that message:

  • If the value of the UDP-Selected variable is 1, the client MUST set the value of the UDP-Selected variable to 0 and MUST set the value of the proto syntax element of the funnelName field in the LinkViewerToMacConnectFunnel (section 2.2.4.18) message to TCP.

  • If the value of the UDP-Selected variable is 0, the client MUST set the value of the UDP-Selected variable to 1 and MUST set the value of the proto syntax element of the funnelName field in the LinkViewerToMacConnectFunnel (section 2.2.4.18) message to UDP and the port syntax element of the funnelName field MUST be set to the value of the UDP-Receive-Port variable.

The client MAY report to the higher layer that it has changed the value of the UDP-Selected variable.

For example, if the first LinkViewerToMacConnectFunnel (section 2.2.4.18) message specifies the protocol as UDP, the second LinkViewerToMacConnectFunnel (section 2.2.4.18) message SHOULD specify the protocol as TCP.

If the client sends a new LinkViewerToMacConnectFunnel (section 2.2.4.18) message, it MUST wait for either a LinkMacToViewerReportDisconnectedFunnel (section 2.2.4.4) message or a LinkMacToViewerReportConnectedFunnel (section 2.2.4.3) message to be received. How to process a LinkMacToViewerReportDisconnectedFunnel (section 2.2.4.4) message is specified in section 3.1.5.5; how to process a LinkMacToViewerReportConnectedFunnel (section 2.2.4.3) message is specified in section 3.1.5.6.

Show:
© 2016 Microsoft