>>>>> On Wed, 08 Jun 2005 09:07:37 +0100, Dave Shield <[EMAIL PROTECTED]> said:
>> 1) aren't all new routine supposed to be prefixed with netsnmp_? Dave> Possibly. Dave> I can't remember whether we ever came to a firm decision. Dave> But it would be easy enough to rename things, as long as Dave> we do so before 5.3 is released. What do people think? I'm pretty sure we came to a good agreement that netsnmp_ prefixes were to be used. I'm not going to look up the discussion though. >> 3) Does it only work via the callback transport? Dave> Not sure. Dave> There's probably no difficulty in using it to query a Dave> remote agent (using any appropriate transport). I'm Dave> not sure what the implications would be about using it Dave> to talk to the same agent - particularly from within a Dave> handler routine. That was my first question too. We've been needing a simple API to use, and I don't think there is a much of a difference between the internal agent needing to query itself and needing to query something external. At least, that was half the point of the callback transport in the first place: to make one API work for everything. IMHO, this type of API should go into the main library and be generic rather than in the agent library. To each his own, however. And, of course, I'm saying this without having looked at that section of code in a long time ;-) -- Wes Hardaker Sparta, Inc. ------------------------------------------------------- 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
