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

chrysn notifications at github.com
Wed Aug 25 16:54:54 CEST 2021


Yes. I'm only using _buf because without it I we couldn't even see *whether* truncation happened, and right here this is all I care about.

> consider this

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

I'm happy to work with this as a proposal, but that'll take several changes and iterations of design, while this here is only about getting the CoAP machinery unstuck when large packages arrive, without any need for applications to alter any behavior. (Unless they specifically checked for whether `memo->state` indicates some particular form of error rather than for success). Let's do both, but please the good before the better.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/16378#issuecomment-905576293
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20210825/766d5c9c/attachment.htm>


More information about the notifications mailing list