mirror of
https://github.com/obgm/libcoap.git
synced 2026-11-04 08:55:40 +03:00
Jon Shallow
21bd1df95b
This means that apps need to have no knowledge of what IP support is available. Updates coap_uri_into_options() and coap_resolve_address_info() which have only been recently added to develop branch and are not in any previous release.
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.