A sequence of messages stored in a byte buffer
Indicates that a message failed its checksum and is corrupt
A message.
A message. The format of an N byte message is the following:
1. 4 byte CRC32 of the message 2. 1 byte "magic" identifier to allow format changes, value is 0 currently 3. 1 byte "attributes" identifier to allow annotations on the message independent of the version (e.g. compression enabled, type of codec used) 4. 4 byte key length, containing length K 5. K byte key 6. 4 byte payload length, containing length V 7. V byte payload
Default constructor wraps an existing ByteBuffer with the Message object with no change to the contents.
Indicates the presense of a message that exceeds the maximum acceptable length (whatever that happens to be)
A set of messages with offsets.
A set of messages with offsets. A message set has a fixed serialized form, though the container for the bytes could be either in-memory or on disk. The format of each message is as follows: 8 byte message offset number 4 byte size containing an integer N N message bytes as described in the Message class
Constants related to messages
Message set helper functions
A sequence of messages stored in a byte buffer
There are two ways to create a ByteBufferMessageSet
Option 1: From a ByteBuffer which already contains the serialized message set. Consumers will use this method.
Option 2: Give it a list of messages along with instructions relating to serialization format. Producers will use this method.