[riot-notifications] [RIOT-OS/RIOT] sys/net/gcoap: Use socket _buf API to recognize truncated requests (#16378)

Martine Lenders notifications at github.com
Wed Aug 25 17:03:54 CEST 2021

> 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...)

Does it oO? If the `coap_pkt_t` struct needs to be extended for `gcoap`'s sake, it might make sense to instead provide an extended, `gcoap`-specific type. But granted, I am not as deep into the `gcoap`/`nanocoap`-internals (yet), to provide solid feedback on this. Up until now I understood that `nanocoap` is only used as a message parser and composer for `gcoap`, but if there is deeper entanglement, maybe some cleanup is indeed required.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20210825/30ffaf88/attachment.htm>

More information about the notifications mailing list