Low-level representation of CoAP messages.
The most notable item in toad_msg is Message;
a CoAP message very close to the actual byte layout.
CoAP messages have some attributes whose size is dynamic: - The message payload (in http terms: the request/response body) - the number of options (in http terms: headers) - the value of an option (in http terms: header value)
Message does not require an allocator and has no opinions about what kind of collection
it uses internally to store these values.
It solves this problem by being generic over the collections it needs and uses a Collection trait
to capture its idea of what makes a collection useful.
This means that you may use a provided implementation (for Vec or tinyvec::ArrayVec)
or provide your own collection (see the custom collections example)
``rust
//! Note: both of these type aliases are exported bytoad_msg` for convenience.
use tinyvec::ArrayVec; use toad_msg::{Message, Opt};
// Message Payload byte buffer
// |
// | Option Value byte buffer
// | |
// | | Collection of options in the message
// vvvvvvv vvvvvvv vvvvvvvvvvvvvvvvv
type VecMessage = Message
// Used like: ArrayVecMessage<1024, 256, 16>; a message that can store a payload up to 1024 bytes, and up to 16 options each with up to a 256 byte value.
type ArrayVecMessage<
const PAYLOADSIZE: usize,
const OPTSIZE: usize,
const NUM_OPTS: usize,
