<p>Sure, that's a change we can make. But it's something that needs coordination across nanocoap and gcoap (which I start suspecting is part of what's holding RIOT's CoAP ecosystem back). In the end, this can get us rid of the need for a payload-sized buffer for incoming messages at all (though so far our handlers place their responses where the request came in, so...)</p>
<p>Does it oO? If the <code>coap_pkt_t</code> struct needs to be extended for <code>gcoap</code>'s sake, it might make sense to instead provide an extended, <code>gcoap</code>-specific type. But granted, I am not as deep into the <code>gcoap</code>/<code>nanocoap</code>-internals (yet), to provide solid feedback on this. Up until now I understood that <code>nanocoap</code> is only used as a message parser and composer for <code>gcoap</code>, but if there is deeper entanglement, maybe some cleanup is indeed required.</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/RIOT-OS/RIOT/pull/16378#issuecomment-905586239">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABE7WYGHVXRTEC5RF4WW773T6UA5VANCNFSM43NLKLAQ">unsubscribe</a>.<br />Triage notifications on the go with GitHub Mobile for <a href="https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675">iOS</a> or <a href="https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email">Android</a>.<img src="https://github.com/notifications/beacon/ABE7WYGVUDMMML4TZELL7SLT6UA5VA5CNFSM43NLKLA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGX5CMPY.gif" height="1" width="1" alt="" /></p>
"name": "View Pull Request"
"description": "View this Pull Request on GitHub",