2.2.3.1 BufferInfo Message
Sends information about the message to follow.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
idContextSrc |
|||||||||||||||||||||||||||||||
|
idContextDest |
|||||||||||||||||||||||||||||||
|
idBuffer |
|||||||||||||||||||||||||||||||
|
nFlags |
|||||||||||||||||||||||||||||||
|
cbSizeBuffer |
|||||||||||||||||||||||||||||||
idContextSrc (4 bytes): An unsigned 32-bit integer. Contains the unique context ID of the sender.
idContextDest (4 bytes): An unsigned 32-bit integer. Contains the unique context ID of the recipient.
idBuffer (4 bytes): An unsigned 32-bit integer. Contains the unique ID for the buffer, which can be any of the following:
Data Buffer: The buffer has a non-null ObjectID (idBuffer) and the memory can be associated with a new DataBuffer instance bearing this handle. No broker creation sequence will precede this transaction; the DataBuffer instance is created implicitly when the data is received.
Individual Message Buffer: The buffer has a NULL ObjectID (idBuffer) and the IsBatch flag will be cleared. The payload can be interpreted as a single message and processed.
Batch Message Buffer: The buffer has a NULL ObjectID (idBuffer) and the IsBatch flag will be SET. The payload can be interpreted as a batch with multiple messages and processed in order.
nFlags (4 bytes): An unsigned 32-bit integer. Describes the BufferFlags.
-
Value
Description
0x00000001
IsBatch. The Buffer is a batch of messages.
-
All other flags are reserved, MUST be ignored, and MUST never be specified.
cbSizeBuffer (4 bytes): An unsigned 32-bit integer. The size of the buffer's data.