2.2.2.4.3.2 Granted Control
The Granted Control order indicates that the sender has accepted control by the receiver.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Msg |
controllerId |
||||||||||||||||||||||||||||||
|
CcontrolGeneration |
|||||||||||||||||||||||||||||||
Msg (2 bytes): MUST be set to 0x0002.
controllerId (2 bytes): The identifier of the user-granted control. This is the user identifier of the node that is in control. If no node is in control, this field is set to zero.
CcontrolGeneration (4 bytes): The initial sequence number of the control operation. Whenever the server receives a Granted Control order, it saves the value in this field as the current control generation sequence number. After the server sends a Granted Control order that contains the current control generation sequence number, it increments that sequence number for use in a future Granted Control order, by the value of the local identifier of the user. This identifier is obtained from S20 packets, such as S20_CREATE or S20_JOIN.
This order is provided for backward compatibility with Microsoft NetMeeting version 2.