On 04/07/07, Robert Story <[EMAIL PROTECTED]> wrote:
> What about simply shortening the name of the leaf files? i.e. :
>
> cd agent/mibgroup/snmp-notification-mib/snmpNotifyFilterTable/*
> rename snmpNotifyFilterTable sNFT snmpNotifyFilterTable*
I wondered about that, but decided against it - for two reasons.
a) readability
snmpNotifyFilterTable is more meaningful than sNFT
b) code impact
changing the names of files means changing the
name of various routines (e.g. the init routine).
Keeping the filenames the same meant that the changes to the
actual code could be kept to a minimum (basically include and
config_require statements).
> If that's not sufficient, mabye moving the sub-directory?
>
> cd agent/mibgroup
> mv snmp-notification-mib/snmpNotifyFilterTable/ notification/
>
> or perhaps both?
Why is it necessary to have a separate subdirectory at all?
There are only three tables in this particular MIB, and it's
architecture independent, so we won't need O/S specific
versions of the data_access handling.
When I moved the all the code together, it didn't feel too
cumbersome. Having an additional subdirectory seems
unnecessary in this particular case, and just serves to
extend the length of the path names.
Dave
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
