benpicco
benpicco
Adding no-response support for NON messages is easy (less than 10 lines in `nanocoap.c`), adding no-response support for CON messages is a whole different effort that I'm still not sure...
> From the request-response layer perspective the addition of an option in said layer should not make any difference, if the underlaying message type is NON or CON *to wait...
Rebased to solve the merge conflict
With #17950 there shouldn't be any actual users of the pointer left - only setters, which can be removed easily.
This needs a rebase, but we can merge this ~~now~~ soon.
Also at run-time. It's just that I've found myself open-coding those way too often, so I thought providing a macro would be appropriate.
How do I test this? What are the expected results before / after this patch?
I had to create a symlink `sudo ln -s libpcap.so.1.8.1 libpcap.so.1.1.1` in `/usr/lib/$(uname -m)-linux-gnu`
Please rebase & squash
looks like KConfig is still missing