3.1.5.1.4 MCS Broadcast Transport Service Functions for S20 Protocol

Nodes use the following MCS functions for the broadcast transport service for the S20 protocol.

Note A "node" in S20 protocol usage is a "user" in MCS. Also, the "MCS Top Provider" is the creator node of an MCS session. The MCS session-creator node can be different from an S20 share-creator node. The MCS session-creator node creates the MCS session. The S20 share-creator node creates the application-sharing session.

Function

Description

MCS_ATTACH_USER

Attaches the node to the MCS session. The S20 protocol node MUST use this function to attach the node to the session before it can create a share session.

MCS_DETACH_USER

Detaches the node from the MCS session. The S20 protocol node MUST use this function to detach itself from the session. This SHOULD happen after a node leaves or ends an application-sharing session.

MCS_SEND_DATA

Sends data to another node or all the nodes in the MCS session. The S20 protocol node uses this function to send all S20 protocol control and data packets.

MCS_CHANNEL_JOIN

Joins a channel in the MCS session. In MCS, every node (user) is associated with a channel automatically. In order for this node to receive data, the node MUST join its local channel. A node in the S20 protocol needs to join its local channel and the S20 protocol node broadcast channel before it can send any S20 protocol control and data packets.

MCS_CHANNEL_LEAVE

Leaves a channel in the MCS session. A node in the S20 protocol needs to leave its local channel and the S20 protocol node broadcast channel after leaving or ending the application-sharing session.