2.2.5.3 NetMeeting Object Manager Lock Grant
An object manager instance replies to the sender of an OMNET_LOCK_REQ packet with an OMNET_LOCK_GRANT packet to indicate a successful workset/object lock attempt.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Sender |
messageType |
||||||||||||||||||||||||||||||
|
wsGroupID |
worksetID |
data1 |
|||||||||||||||||||||||||||||
|
reserved |
|||||||||||||||||||||||||||||||
Sender (2 bytes): The local identifier of the user, which is obtained from the Multipoint Communication Service (MCS) [T122] layer. For more information about the MCS user ID, see [T122] section 3 (Definitions) in the ITU-T Recommendation.
messageType (2 bytes): MUST be set to 0x0016.
wsGroupID (1 byte): The workset group ID (unique to the domain). This value is generated internally by the NetMeeting Object Manager. It consists of a value from 0 to 63 that is checked for uniqueness among other NetMeeting nodes present on the network.
worksetID (1 byte): An 8-bit workset ID defined within a workset group.
data1 (2 bytes): An unsigned 16-bit integer correlator.
reserved (4 bytes): Reserved. MUST be set to zero when sent and MUST be ignored on receipt.