Description

Unlike with shell commands, there is only one provided-by-default Gcoap resource, and that's .well-known/core and kind of special.

For CoAP to become as usable as the shell, it'd be useful to have opt-in modules for CoAP resources just like for shell commands (ps etc), see forum discussion. More generally, this could help make CoAP programs more composable, at least where resources don't need userargs passed in by the application.

One way for this might be to have them XFA'd into the _default_resources listener we already have. I'd like to give that a try, pre-implementation input would be helpful. (Especially "I tried that, didn't work because of X").