Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve /.well-known/core Handler #15

Open
NZSmartie opened this issue Mar 26, 2017 · 2 comments
Open

Improve /.well-known/core Handler #15

NZSmartie opened this issue Mar 26, 2017 · 2 comments

Comments

@NZSmartie
Copy link
Contributor

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.

@tothero
Copy link
Member

tothero commented Oct 23, 2017

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.

@niondir
Copy link
Member

niondir commented Dec 4, 2017

"soon" is relativ. It's not clear when we find time to spend on this. So help is always welcome. We let you known in case we start on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants