2008/11/11 Need Help <[EMAIL PROTECTED]>: > I have noticed that the "xxxxxEntry" and "xxxxxIndex" oids which are used to > define a Table are marked as "non-accessible", instead of "read-only". > > Why advantages do you get for defining it as "non-accessible" vs > "read-only"?
That's the wrong question. What advantages would you get by defining these as "read-only" rather than "not-accessible"? Remember, there is no information associated with the table as a whole. The information is associated with individual "cells" of the table - a particular instance of one of the columns. So the column object is defined as "read-only" or better. But the table infratstructure objects are defined as "not-accessible", because there's no information associated with them. Dave ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
