The CoAP Draft 18 describes an endpoint as: "A CoAP Endpoint is is identified by transport layer multiplexing information that can include a UDP port number and a security association." (draft-ietf-core-coap-14: 1.2)
The following diagram describes the structure of an endpoint. The endpoint implements CoAP in layers. Incoming and outgoing messages always travel from layer to layer. An {@link Exchange} represents the known state about theexchange between a request and one or more corresponding responses. The matcher remembers outgoing messages and matches incoming responses, acks and rsts to them. MessageInterceptors receive every incoming and outgoing message. By default, only one interceptor is used to log messages.
+-----------------------+ | {@link MessageDeliverer} +--> (Resource Tree)+-------------A---------+ | * A +-Endpoint--+-A---------+ | v A | | v A | | +---------v-+-------+ | | | Stack Top | | | +-------------------+ | | | {@link TokenLayer} | || +-------------------+ | | | {@link ObserveLayer} | || +-------------------+ | | | {@link BlockwiseLayer} | || +-------------------+ | | | {@link ReliabilityLayer} | || +-------------------+ | | | Stack Bottom | | | +--------+-+--------+ | | v A | | v A | | {@link Matcher} || v A | | {@link MessageInterceptor} | | v A | | v A | | +--------v-+--------+ | +-| {@link Connector} |-++--------+-A--------+ v A v A (Network) The endpoint and its layers use an {@link ScheduledExecutorService} toexecute tasks, e.g., when a request arrives.
| |
| |
| |
| |
| |
| |