Low-level representation of CoAP messages.
alloc
vs no_alloc
kwap_msg implements CoAP messages as either backed by:
- alloc
: dynamically growable heap-allocated buffers
- no_alloc
: static stack-allocated buffers
alloc::Message
can be much easier to use and performs comparably to no_alloc
, however it does require:
std
or a global allocator
This crate uses criterion
to measure performance of the heaped & heapless implementations in this crate as well as coap_lite::Packet
.
In general, kwap_msg::alloc::Message
is faster than coap_lite, which is much faster than no_alloc::Message
.
Benchmarks:
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.