Buffer interface, which does not have any internal cursors unlike ByteBuffer of Java library.
Buffer interface, which does not have any internal cursors unlike ByteBuffer of Java library.
- The read methods read the buffer data from the given position. - The write methods write data to the specified position in the buffer and return the written byte length.
If the buffer capacity is insufficient, these read/write methods throw an InsufficientBufferException. If this exception is thrown, the user code should feed more data, and then resume reading.
This error is thrown when the user tries to read an integer value using a smaller types.
This error is thrown when the user tries to read an integer value using a smaller types. For example, calling MessageUnpacker.unpackInt() for an integer value that is larger than Integer.MAX_VALUE will cause this exception.
Base class for message pack errors
Provides a buffered output stream that writes sequence of WriteBuffer instances.
Provides a buffered output stream that writes sequence of WriteBuffer instances.
A Sink implementation has total control of the buffer memory so that it can reuse buffer memory, use buffer pools, or use memory-mapped files.
Message Packer interface
Mutable cursor for Unpacker.
MessageUnpacker interface
MessagePack prefix codes
For compatibility with Scala, Scala.js
Describes the list of the message format types defined in the MessagePack specification.
Write MessagePack code at a given position on the buffer and return the written byte length
Read a message pack data from a given offset in the buffer.
Read a message pack data from a given offset in the buffer. The last read byte length can be checked by calling ReadCursor.lastReadLength method.
Representation of MessagePack value types.