mirror of
https://github.com/obgm/libcoap.git
synced 2026-11-04 00:45: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 client example
This example shows how to configure a client to use libcoap
Fast configuration (Between RIOT instances):
Preparing the logical interfaces:
sudo ./../../dist/tools/tapsetup/tapsetup --create 2
Client invocation
For the client:
PORT=tap0 make term
coapc
The IP address to connect to needs to be that as returned by libcoap_server, or that of the tap0 interface, etc.
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.