On Wednesday, 28 February 2018 12:19:48 PST Nash, George wrote: > So far in all of the services that I have developed I have always created > the resource as soon as the service is started. > > However, CRUDN is CREATE, READ, UPDATE, DELETE, NOTIFY. > > I CREATE the resource at service start as part of the initialization code. > Should I wait for a client action before creating a resource? > > What about DELETE? I don't think any of my services can delete resources.
That's normal, for both situations. Some services will have create/delete interaction, most will not. You're going to see them usually only on non-physical services, like creating a group of devices, a scene, an ACL, etc. If you have a physical or fixed service, then it already exists and cannot be deleted (short of transferring ownership to another user). > Are there any samples that show CREATE and DELETE? Since security > permissions map directly to the CRUDN I wanted to understand how CRUDN > actually maps to code. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
