CoAP and FOREST

It looks like there could be a cleaner mapping from my FOREST architectural style to CoAP than there is to HTTP.

FOREST stands for "Functional Observer REST" - it's based on objects observing each other's states, either locally or over the network.

FOREST uses GET and POST to transfer object state between objects. GET is used to read or poll the state of a linked object, and POST to notify either a new object state of interest or an updated object state to a peer object already known to be interested.

CoAP has observation built-in, unlike HTTP.

I implemented my own HTTP stack in NetMash, but CoAP seems a bit more complicated, even when I take out the bits I don't need. Still, I'll be keeping CoAP in my radar.