Expand description
A CoAP endpoint that can be used for 1-to-1 communication.
This can act both as a “server” and “client”, which means that requests can be sent in both
directions via a single connection.
As stated in RFC 7252, Section 4.8,
the Endpoint assumes NSTART = 1.
This means that at any given time, only one single outgoing request and
one single incoming request (including sending the corresponding response) can be handled.
This Endpoint does not implement a listening server. So it is not possible to listen to a port and handle any incoming connection. Instead, only 1-to-1 connections can be established via ip, uri or socket.
Currently, the Token size is fixed to 8 bytes (or 0 for Empty messages).
Modules§
- connect
- Connection Layer of the CoAP Endpoint
- error
- Error used by the CoAP-Zero Endpoint
- incoming
- The incoming communication path
- outgoing
- The outgoing communication path
Structs§
- Coap
Endpoint - Endpoint for 1-to-1 connection to another CoAP Endpoint
- Retransmission
State - Stores the current (re)transmission state for the current message and implements the exponential backoff strategy for retransmissions
- Retransmission
Timeout - Error type for
RetransmissionState::retransmit_required - Transmission
Parameters - Parameters of a CoAP Endpoint
Enums§
- Endpoint
Event - Events that are generated on the endpoint-level
Constants§
- DEFAULT_
COAP_ PORT - The default port the CoAP via UDP Protocol communicates on
Type Aliases§
- Uri
- Type alias for an iri_string URI