2.2.5.22.2 NetMeeting Object Manager WSGROUP_REG_REC
A WSGROUP_REG_REC (WORKSET GROUP REGISTRATION OBJECTS) structure identifies a node's usage of a workset group. These objects can reside in any ObManControl (Object Manager Control) workset. In the case of workset #0, these objects identify a node's usage of the ObManControl workset group itself. Since all instances of ObMan in a Domain are used, the ObManControl workset group, the registration objects in workset #0 form a complete list of all the instances of ObMan in a Domain.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
length |
|||||||||||||||||||||||||||||||
|
idStamp |
|||||||||||||||||||||||||||||||
|
userID |
status |
||||||||||||||||||||||||||||||
|
person (48 bytes) |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
|
handle |
|||||||||||||||||||||||||||||||
length (4 bytes): The byte length of this data packet, exclusive of the byte length of this field.
idStamp (4 bytes): An unsigned 32-bit integer initialized using the following algorithm.
Initialize four input parameters: X1, X2, X3, and X4. This can be done using any implementation-specific method. This algorithm MUST be able to accept any generic datatype as a parameter. This algorithm MUST type cast the parameters as unsigned 32-bit integers before performing any operations with them.
Initialize an unsigned, 32-bit integer I to 0.
Bitwise-OR X1 with I, and store the result in I.
Left-shift X2 by 8 bits and Bitwise-OR the new value with I. Store the result of the OR operation in I.
Left-shift X3 by 16 bits and Bitwise-OR the new value with I. Store the result of the OR operation in I.
Left-shift X4 by 24 bits and Bitwise-OR the new value with I. Store the result of the OR operation in I.
Initialize idStamp with the value stored in I.
-
This algorithm can be represented algebraically using the following expression.
-
idStamp = X1+X2*256+X3*65536+X4*16777216;
-
userID (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.
status (2 bytes): An unsigned 16-bit integer state field set to either 1 = CATCHING_UP or 2 = READY_TO_SEND.
person (48 bytes): The name of the node. MUST be present as an array of UCHAR.
handle (4 bytes): Reserved. MUST be set to zero when sent and MUST be ignored on receipt.