Zephyr API Documentation
3.7.0
A Scalable Open Source RTOS
|
CoAP implementation for Zephyr. More...
Go to the source code of this file.
Data Structures | |
struct | coap_core_metadata |
In case you want to add attributes to the resources included in the 'well-known/core' "virtual" resource, the 'user_data' field should point to a valid coap_core_metadata structure. More... | |
Macros | |
#define | COAP_WELL_KNOWN_CORE_PATH ((const char * const[]) { ".well-known", "core", NULL }) |
This resource should be added before all other resources that should be included in the responses of the .well-known/core resource if is to be used with coap_well_known_core_get. | |
Functions | |
int | coap_well_known_core_get (struct coap_resource *resource, const struct coap_packet *request, struct coap_packet *response, uint8_t *data, uint16_t data_len) |
Build a CoAP response for a .well-known/core CoAP request. | |
int | coap_well_known_core_get_len (struct coap_resource *resources, size_t resources_len, const struct coap_packet *request, struct coap_packet *response, uint8_t *data, uint16_t data_len) |
Build a CoAP response for a .well-known/core CoAP request. | |
CoAP implementation for Zephyr.