On Sun, 17 Jun 2007 15:11:26 +0100 Dave wrote: DS> I'm just thinking that if we're looking to separate out the data_access code, DS> it would be appropriate to try and ensure that these routines are as DS> "MIB-agnostic" as possible - that the coding used for a given data_access DS> module shouldn't restrict the choice of MIB coding style.
So, by 'MIB-agnostic', I'm assuming you just mean nothing specific to a particular handler... e.g. embedded netsnmp_containers or next/prev pointers. What about a member for the actual MIB index? Especially for cases where the index is in no way related to any existing data for the item (eg hrDeviceId / hrDiskStorageTable). The other thing I'd really like to do is standardize on how the data collection is accessed. As you might expect, I'm partial to netsnmp_containers. ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
