mirror of
https://github.com/obgm/libcoap.git
synced 2026-11-09 02:32:53 +03:00
Jon Shallow
26cd2446a8
examples/contiki/coap-observer.c: examples/etsi_iot_01.c: include/coap2/coap_prng.h: include/coap2/net.h: src/coap_debug.c: src/coap_openssl.c: src/coap_session.c: src/net.c: src/option.c: tests/test_error_response.c: tests/test_options.c: prng -> coap_prng prng_init -> coap_prng_init coap_option_setb -> coap_option_filter_set coap_option_clrb -> coap_option_filter_unset coap_option_getb -> coap_option_filter_get include/coap2/coap.h.windows: win32/libcoap.vcxproj: win32/libcoap.vcxproj.filters: prng.h -> coap_prng.h include/coap2/option.h: Add in COAP_DEPRECATED in deprecated functions.
Example of libcoap running on contiki
=====================================
To run the example, do
$ make
$ sudo ./server.minimal-net
(and in a second terminal)
$ sudo ip -6 a a aaaa::1/64 dev tap0
and query `coap://[aaaa::1000]/time?ticks` with any coap tool,
or query `coap://[aaaa::1000]/.well-known/core`
This will
* download contiki from the upstream git sources
* build the server application
* run the server application, creating a virtual network device tap0 (unless
that exists)
* configure your network interface to make the server accessible.
* return the appropriate response from the server to the client.
The server creates a resource for 'time' with a query 'ticks'. This is
reported for `.well-known/core`. The work flow for adding more resources does
not differ from regular libcoap usage. If you seem to run out of memory
creating the resources, tweak the number of pre-allocated resources
in `coap_config.h.contiki`.