>>>>> On Thu, 05 May 2005 17:07:36 +0100, Dave Shield <[EMAIL PROTECTED]> said:
Dave> I've come up with the following list of required tasks facing such Dave> a helper. What else (or different) would it need to provide? Dave> SNMP-request handling: Dave> - register (and unregister) the table Dave> - add or remove a row to/from the table Dave> - retrieve the row relating to a specific varbind request Dave> (this may possibly need to retrieve both the helper's Dave> representation of the row, and the data relating to it, Dave> if these are different) Dave> - retrieve the indexes relating to this row (?) Dave> External handling Dave> - retrieve a particular row (specified by index) Dave> - walk through the rows of the table (order not important) Dave> I *think* that should cover all requirements. What have I missed? I think there are actually 2 cases (Robert and I have been arguing about this for ages): 1) data stored internally in our MIB structures. 2) data stored externally And how you treat them is entirely different some of the time. EG, for #1 we need routines to easily access the stored data. I'm sure an ideal thing for most people would be a variable-argument function to return data based on values passed: get_my_darn_data(tableptr, indexval1, indexval2, ...) because that's how this discussion got started because we've failed to provide such an API for much of our work. Iterating is nice, but really even that requires them to loop when we could do it for them most of the time. -- Wes Hardaker Sparta, Inc. ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders