1c87c5fbaSopenharmony_ciExample of libcoap running on Contiki-NG
2c87c5fbaSopenharmony_ci========================================
3c87c5fbaSopenharmony_ci
4c87c5fbaSopenharmony_ciTo run the example, do
5c87c5fbaSopenharmony_ci
6c87c5fbaSopenharmony_ci    $ make
7c87c5fbaSopenharmony_ci    $ sudo ./server.native
8c87c5fbaSopenharmony_ci
9c87c5fbaSopenharmony_ciand query `coap://[fd00::302:304:506:708]/time?ticks` with any coap tool,
10c87c5fbaSopenharmony_cior query `coap://[fd00::302:304:506:708]/.well-known/core`
11c87c5fbaSopenharmony_ci
12c87c5fbaSopenharmony_ciThis will
13c87c5fbaSopenharmony_ci
14c87c5fbaSopenharmony_ci* download Contiki-NG from the upstream git sources
15c87c5fbaSopenharmony_ci* build the server application
16c87c5fbaSopenharmony_ci* run the server application, creating a virtual network device tap0 (unless
17c87c5fbaSopenharmony_ci  that exists)
18c87c5fbaSopenharmony_ci* configure your network interface to make the server accessible.
19c87c5fbaSopenharmony_ci
20c87c5fbaSopenharmony_ci* return the appropriate response from the server to the client.
21c87c5fbaSopenharmony_ci
22c87c5fbaSopenharmony_ciThe server creates a resource for 'time' with a query 'ticks'.  This is
23c87c5fbaSopenharmony_cireported for `.well-known/core`. The work flow for adding more resources does
24c87c5fbaSopenharmony_cinot differ from regular libcoap usage.
25