3.1.5.1 Processing the Common PDU Header
The Type field (as specified in Common Order Header (ORDER_HDR) (section 2.2.1)) MUST be examined to determine if it corresponds to a known message type. If the type does not correspond to a known message type, the PDU SHOULD be ignored.<7> If the type matches a known type, the processing for the Length field (see Common Order Header (ORDER_HDR) (section 2.2.1)) MUST be performed based on the value of the Type field, as described in the following table.
|
Type field value |
Processing instructions |
|---|---|
|
ODTYPE_FILTER_STATE_UPDATED 0x0001 |
|
|
ODTYPE_APP_REMOVED 0x0002 |
|
|
ODTYPE_APP_CREATED 0x0003 |
|
|
ODTYPE_WND_REMOVED 0x0004 |
|
|
ODTYPE_WND_CREATED 0x0005 |
|
|
ODTYPE_WND_SHOW 0x0006 |
|
|
ODTYPE_PARTICIPANT_REMOVED 0x0007 |
|
|
ODTYPE_PARTICIPANT_CREATED 0x0008 |
|
|
ODTYPE_PARTICIPANT_CTRL_CHANGE 0x0009 |
Processing the Change Participant Control Level PDU (section 3.3.5.2.3) |
|
ODTYPE_GRAPHICS_STREAM_PAUSED 0x000A |
|
|
ODTYPE_GRAPHICS_STREAM_RESUMED 0x000B |
Processing a Graphics Stream-Resumed PDU (section 3.2.5.3.2) |
|
ODTYPE_WND_REGION_UPDATE 0x000C |
|
|
ODTYPE_PARTICIPANT_CTRL_CHANGE_RESPONSE 0x000D |
Processing the Change Participant Control Level Response PDU (section 3.2.5.2.3) |
More than one sharing message can be contained in a single virtual channel payload. If more than one message is included, they are concatenated, with each message having its own common message header. When processing a message, the receiver MUST verify that enough network data remains in the virtual channel packet to process a message of the size specified by the Length field. The receiver SHOULD disconnect from the sharing session if there is not enough data.<8>