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. All of the samples that I have looked at use GET, PUT, and POST. GET corresponds to the READ. In all the examples I has seen both PUT and POST both map to UPDATE they can cause the resource to NOTIFY observers about any change. 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. Thanks George Nash
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
