On Fri, 15 Jun 2007 10:21:58 +0100 Dave wrote: DS> So what you are proposing is effectively something like: DS> DS> svn move agent/mibgroup/hardware agent/mibgroup/data_access DS> (plus various similar moves, and consequent tweaking of related code) DS> DS> Correct?
Yep. DS> What sort of structure did you have in mind for 'data_access'? DS> Relatively flat (d_a/memory, d_a/ip, d_a/software)? DS> Or some form of internal grouping (d_a/hardware/memory, DS> d_a/network/ip, d_a/software/proc)? I could go either way, with a slight preference for the latter. DS> How similar are the container mechanisms currently used for (e.g.) DS> MfD-style data_access routines, compared to the HAL code? I'm peeked at the cpu code, and the big difference that I see is that it looks like you provide an iterator interface (get/next), whereas I generally just return a container. DS> I seem to remember you floating the idea of consolidating the MfD DS> internal table representation, with that used for the table_tdata helper. DS> [...] DS> Would this perhaps be a good time to review that idea, and try DS> to increase the amount of commonality in the MIB implementation DS> frameworks? Sure. Did you have anything in particular in mind? I haven't looked at the tdata helper in a while, and only vaguely remember the previous discussion... ------------------------------------------------------------------------- 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
