Anurag S. Maskey wrote:
> How is the read-only property used in other entities? I've been assuming 
> that the user can set this property if s/he doesn't want values of other 
> properties to change. So, it is a user-configurable property. Hence, my 
> question about adding read-only to WLANs. Is this its intended use?
>
>   
Not sure what others think, but I suppose
the original use case was more about fencing
off aspects of the configuration from modification
by the user. If that's the only intended use case, my
inclination would be to hide the read-only property
value from walk and setprop operations so that users
can't toggle it for other objects. I'm not sure that
there's much benefit in making other objects like
locations, ENMs and WLANs read-only, but I could
be missing something here.

Also, Anurag and I were discussing the current
scheme, whereby nwamd uses an OKAY_TO_WRITE
flag to allow it to write to readonly objects in
libnwam calls, whereas other libnwam consumers do
not. It occurred to me that since what we really want
to do is to restrict modification of these objects
to nwamd itself, would it maybe make sense
rather than having a readonly property
to simply do a check of the uid of the library
caller - if it matches the netcfg uid (that nwamd
runs as) we can modify the automatic NCP, otherwise
we can't. Anurag pointed out that if this was the
approach we took, we could simply su
to the netcfg user and modify things via nwamcfg,
but I don't know if that's a major problem. What do
you think?

Alan
> Thanks,
> Anurag
>
>
> Anurag S. Maskey wrote:
>   
>> Should the Known WLAN object also have a "read-only" property consistent 
>> with ENM's and Locations? Makes sense to me.
>>
>> Anurag
>> _______________________________________________
>> nwam-dev mailing list
>> nwam-dev at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/nwam-dev
>>   
>>     
> _______________________________________________
> nwam-dev mailing list
> nwam-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/nwam-dev
>   


Reply via email to