Re: MAX-ACCESS of table index
"Dave Shield" <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
On 14/12/06, [email protected] <[email protected]> wrote: > I have a doubt regarding table index. In MIB table sometimes the index > is not-accessible and some time the index is read-only. > My doubt is how to decide whether the table index will be read-only or > not-accessible. As long as there is at least one non-index column in the table, then the indexes themselves should be "not-accessible". End of Story. There are many examples where this is not true - typically down to historical reasons, or poor MIB design. And it does also make things easier for lazy client application programmers. But there is *no* need to define index objects as accessible (whether for notifications, read or write access). The *only* time you need to do so is when there are no non-index columns in the table (e.g. the udpTable). In all other circumstances, you can work with one of the non-index columns, and you get the index values for free (as part of the OID). Dave ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users