You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regarding the default /.well-known/core handler; I think adding a CoAP_RemoveResource(...) to complement CoAP_CreateResource(...) would enable the application to remove the default handler and help by allowing the application to dynamically remove resources as they disappear from the device (for what ever reason).
Another idea is allowing the application layer to manually register WellKnown_GetHandler (Might rename it to CoAP_DefaultWellKnownHandler for clarity). Or possibly adding a flag to CoAP_Config_t to disable automatic registration of the default handler
otherwise, maybe a callback could be added to CoAP_ResOpts_t When it's not null, WellKnown_GetHandler will call that for generating a string (i.e. </example/resource>;ct="0 50 60";rt="example";if="sensor") per resource.
The text was updated successfully, but these errors were encountered:
Will be added soon. We redesign the stack in a way that we use ONE linked list lib. With this improvement it's no problem to add it dynamically. Stay tuned.
Regarding the default
/.well-known/core
handler; I think adding aCoAP_RemoveResource(...)
to complementCoAP_CreateResource(...)
would enable the application to remove the default handler and help by allowing the application to dynamically remove resources as they disappear from the device (for what ever reason).Another idea is allowing the application layer to manually register
WellKnown_GetHandler
(Might rename it toCoAP_DefaultWellKnownHandler
for clarity). Or possibly adding a flag toCoAP_Config_t
to disable automatic registration of the default handlerotherwise, maybe a callback could be added to
CoAP_ResOpts_t
When it's not null,WellKnown_GetHandler
will call that for generating a string (i.e.</example/resource>;ct="0 50 60";rt="example";if="sensor"
) per resource.The text was updated successfully, but these errors were encountered: