Scott Bertin

The #defines I have are more for features than for API compatibility. I know some of my changes are not compatible with the 1.0 API.

I think it should be investigated before closing.

I see the value in being able to build with different CoAP libraries, but I think Wakaama is closely tied to the CoAP code right now. I think we should...

I think enhancement is good. Go ahead and change it.

If I am understanding your response correctly, a Read of a Multiple Resource with no instance would return a response code of 2.05 Content with no payload. If it was...

> > If I am understanding your response correctly, a Read of a Multiple Resource with no instance would return a response code of 2.05 Content with no payload. >...

A slight modification to Proposal B would be to simply omit the instance ID. Here is an example based on Example B.1: ``` CoAP POST Uri-Path:"/11" Content-Format:application/senml+json Payload: [ {...

I'd prefer not having yet another communication channel I need to keep up with. It could also have discussions about issues become disassociated with the issue.

I'm also in favor of a code standard with no strong opinions on the specifics. If it can easily be automated and enforced even better.

This is in reference to https://github.com/eclipse/wakaama/pull/602#issuecomment-836774135. It seems off topic there. A pure cosmetic patch which reformats just the portion of code changed creates a burden on the developer. They...