Hi Esko,
Hi list,
> could there be a new CoAP Option to express a particular path like
> "/.well-known/foo" into a very short option e.g. 1 or 2 bytes overhead?
I would assume this as "over optimization".
Would it be possible to have some relevant examples along with the
number of bytes in total and savings?
In my experience, "/.well-known" is used mainly once at the begin of a
sequence of request. It usually respond with a larger payload. Saving 10
bytes doesn't pay off in scenarios, where 1000 bytes are in use.
br
Achim
Am 21.07.25 um 16:11 schrieb Esko Dijk:
Just an idea that came up here in the ANIMA WG:
could there be a new CoAP Option to express a particular path like
"/.well-known/foo" into a very short option e.g. 1 or 2 bytes overhead?
That could mitigate some concerns about using "/.well-known" type paths
which today adds many bytes of overhead to a message which has little
value because always identical for a particular application.
The receiver is of course assumed to know this option, just like it
would know (guaranteed by system/solution design) the "/.well-known/foo"
path otherwise.
A related idea is just an option to encode "/.well-known" in short form.
thanks for any feedback/reactions you may have ;)
Esko
_______________________________________________
core mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
Anima mailing list -- [email protected]
To unsubscribe send an email to [email protected]
