> > > 1. first search public props > > > 2. if not found, try the wifi props > > > > Aren't the WiFi properties public? > > they are a special case of public: as I mentioned in the design doc, > the system calls for these are written as discrete ioctls to the > net80211 module, so they don't follow the same DLDIOCSETPROP path > as the "True" public properties.
Right, but the above list makes it sound like they're not public properties. How we implement them is a separate matter. > > ... and if a public property with the same name is subsequently added, it > > becomes impossible to access the private property? > > correct. But Private properties are not designed to linger for > extended periods of time. There's a danger of them being abused > (much like ndd was), and I'm not sure it's a good idea to build > too much infra-structure around these. I'm not concerned about lingering, I'm concerned about creating an architecture where things can break in a patch -- or where we're unable to introduce new public properties in a patch -- and neither seems acceptable. -- meem
