mirror of
https://github.com/obgm/libcoap.git
synced 2026-11-08 02:22:54 +03:00
Jon Shallow
084c866c69
This then makes sure that all things libcoap are properly initialized before use, and coders realize they need to do this. Note: coap_new_context() continues to make sure that coap_startup() is invoked if not done previously, but this may be too late.
libcoap server example
This example shows how to configure a server to use libcoap
Fast configuration (Between RIOT instances):
Preparing the logical interfaces:
sudo ./../../dist/tools/tapsetup/tapsetup --create 2
Server invocation
For the server:
PORT=tap0 make term
coaps {stop|start}
The server supports requests for coap://[ip]/time?ticks coap://[ip]/.well-known/core
Handling the static memory allocation
libcoap for RIOT is using the sys/memarray module and therefore there
are certain limits. Said resources are defined in libcoap/src/coap_mem.c,
but can be overwritten at compile time.