5) thus, I would choose one of: a) have the new behaviour to probe later with a new flag to probe immed. b) have the new behaviour to have a new flag to probe later c) leave as existing
Obviously c is what we're trying to avoid, b is probably safer but I think we should do a because I doubt it'll affect anyone and if it does it'll be 1) experts and 2) 1-2 people at most I'd think. We could always revert it later if I'm wrong.
I'm one of those who will be affected by option a, and I'm not sure that I'm an expert ;). By the current API openning a session was the only way available to discover the engine without duplicating or altering code. What is needed IMHO is an explicit API to discover the engine.
It seems to me that I fail to understand the reason for changing the current behaviour. What is the point of sending an snmpv3 GET to an agent which does not support snmpv3? maybe I'm mistaken but isn't it the same as resolving the dns address when openning a session?
Mark.
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.17 - Release Date: 19.04.2005
------------------------------------------------------- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
