On Wed, 2005-06-08 at 17:14, Wes Hardaker wrote: Robert> 1) aren't all new routine supposed to be prefixed with netsnmp_? Wes> I'm pretty sure we came to a good agreement that netsnmp_ Wes> prefixes were to be used.
Fair enough. I wasn't particularly happy with some of the names anyway. Changing them is no great hardship. Robert> 3) Does it only work via the callback transport? Wes> We've been needing a simple API to use, and I don't think there Wes> is a much of a difference between the internal agent needing to Wes> query itself and needing to query something external. Wes> IMHO, this type of API should go into the main library and be Wes> generic rather than in the agent library. That idea hadn't occurred to me, but you're probably right. Certainly the "query on this session" routines make sense in the main library. The versions that rely on an internally shared callback session are probably specific to the agent, but can obviously continue to use the session-based calls to do the work. <tap, tap, tap, make, tap, tap> OK - now done. All routines have been renamed with "netsnmp_" prefixes, and the session-based interfaces are now in the main SNMP library. Dave ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
