Crate liboscore_msgbackend

Backend for liboscore’s native message API

This is (and, unless one wants to go through Box<dyn ReadableMessage>) necessarily a bit opinionated, in that it binds to a concrete message type (or set thereof).

It wraps different implementations of coap-message in an enum.

Structs

• oscore_msg_native_optiter_t
• oscore_msg_native_t
  The message type is conveniently already more pointer-like; given that we pass around pointers to a concrete type (albeit possibly an enum), it’s just that.

Enums

• c_void
  Void stand-in recognized by the cbindgen library by its name
• oscore_msgerr_native_t
  Errors out of message operations

Traits

• WithMsgNative
  Sealed helper trait to implement with_msg_native

Functions

• oscore_msg_native_append_option
• oscore_msg_native_get_code
• oscore_msg_native_map_payload
• oscore_msg_native_optiter_finish
• oscore_msg_native_optiter_init
• oscore_msg_native_optiter_next
• oscore_msg_native_set_code
• oscore_msg_native_trim_payload
• oscore_msg_native_update_option
• oscore_msgerr_native_is_error
• with_inmemory_as_msg_native
  Make a coap_message_implementations::inmemory_write::Message usable as a [raw::oscore_msg_native_t]