2.2.4 Payload Messages
Payload messages are used to issue rendering and sound commands. Payload messages are sent in client-byte order, as determined by the extender capabilities exchange.
Every payload message has the standard header listed in the following table.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
_size |
|||||||||||||||||||||||||||||||
_msgid |
|||||||||||||||||||||||||||||||
_idObjectSubject |
_size (4 bytes): An unsigned 32-bit integer. Describes the total message size, in bytes.
_msgid (4 bytes): A signed 32-bit integer. The message ID that is unique to the specific target. The value specified in _msgid is used to indicate which action to take on the target object.
_idObjectSubject (4 bytes): An unsigned 32-bit integer. The ID of the target object. The _idObjectSubject refers to an object that was previously created by sending a Broker_CreateObject payload.