[riot-notifications] [RIOT-OS/RIOT] net/gcoap: add functions to read and set the next message id (#16730)

chrysn notifications at github.com
Fri Aug 13 19:18:20 CEST 2021


That does make sense (although I'm surprised it is hit ...
EXCHANGE_LIFETIME defaults to 247 seconds, but yeah at 100 requests per
second this hits 50-50 on reaching the cache after a reboot, and at 10/s
it's still 4% by the back of the envelope).

API-wise, I'd suggest a different approach though:

gcoap could define an opaque type (OK no such thing in C, but say in the
docs that the fields may change) describing its state, with a
`gcoap_hibernate_dump(*type)` and a `gcoap_resume_from(const *type)`
function. The type's content would depend on build flags, would always
contain MIDs but possibly also token (making reboots unnoticable to
those observing token values) and possibly DTLS or OSCORE resumption
data later.

Of course, if as Ben suggested it's all just about lack of randomness,
then the same approach applies but to the RNG ;-)


-- 
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/16730#issuecomment-898607884
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20210813/e4c46077/attachment.htm>


More information about the notifications mailing list