79e6b0e0f6
As of today <zephyr/zephyr.h> is 100% equivalent to <zephyr/kernel.h>. This patch proposes to then include <zephyr/kernel.h> instead of <zephyr/zephyr.h> since it is more clear that you are including the Kernel APIs and (probably) nothing else. <zephyr/zephyr.h> sounds like a catch-all header that may be confusing. Most applications need to include a bunch of other things to compile, e.g. driver headers or subsystem headers like BT, logging, etc. The idea of a catch-all header in Zephyr is probably not feasible anyway. Reason is that Zephyr is not a library, like it could be for example `libpython`. Zephyr provides many utilities nowadays: a kernel, drivers, subsystems, etc and things will likely grow. A catch-all header would be massive, difficult to keep up-to-date. It is also likely that an application will only build a small subset. Note that subsystem-level headers may use a catch-all approach to make things easier, though. NOTE: This patch is **NOT** removing the header, just removing its usage in-tree. I'd advocate for its deprecation (add a #warning on it), but I understand many people will have concerns. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| src | ||
| CMakeLists.txt | ||
| README.rst | ||
| docker-test.sh | ||
| prj.conf | ||
| sample.yaml | ||
README.rst
.. _coap-server-sample: CoAP Server ########### Overview ******** This sample is a simple CoAP server showing how to expose a simple resource. This demo assumes that the platform of choice has networking support, some adjustments to the configuration may be needed. The sample will listen for requests in the CoAP UDP port (5683) in the site-local IPv6 multicast address reserved for CoAP nodes. The sample exports the following resources: .. code-block:: none /test /seg1/seg2/seg3 /query /separate /large /location-query /large-update These resources allow a good part of the ETSI test cases to be run against coap-server. Building And Running ******************** This project has no output in case of success, the correct functionality can be verified by using some external tool such as tcpdump or wireshark. See the `net-tools`_ project for more details This sample can be built and executed on QEMU or native_posix board as described in :ref:`networking_with_host`. Use this command on the host to run the `libcoap`_ implementation of the ETSI test cases: .. code-block:: console sudo ./examples/etsi_coaptest.sh -i tap0 2001:db8::1 To build the version supporting the TI CC2520 radio, use the supplied prj_cc2520.conf configuration file enabling IEEE 802.15.4. .. _`net-tools`: https://github.com/zephyrproject-rtos/net-tools .. _`libcoap`: https://github.com/obgm/libcoap