I am implementing the enforcement of read-only properties and objects in the library. So far, I've added a boolean flag (called read_only) in the handle for ENM, LOC, and NCU. This flag is set from the "read-only" property when an object is read in (i.e., selected in nwamcfg terms).
The nwam_ncu_set_prop_value() performs validity checking every time the value is changed. It will also check if the object is read-only. I propose adding "flags" to this function so that the read-only enforcement can be overwritten (as in nwam_*_commit() and nwam_*_destroy() functions with the NWAM_FLAG_OKAY_TO_WRITE). Also, add flags to create and delete so that the read-only property can be overwritten. The reason for this is to allow nwamd to create NCU's and change properties of the read-only NCU's. Also, the library should not allow properties of read-only objects to be set, and then later reject a commit for those changes. We already check validity of values and reject setting invalid values. By extension, the flags would be added to the respective enm, loc, and wlan functions also. (BTW, should nwamd be able to override the read-only property of these objects?) Comments? Thanks, Anurag
