On Sat, 2005-09-03 at 11:16 -0700, David T. Perkins wrote:
> But back to the fundamental question...
> Should the semantics associated with objects be allowed to
> use attributes of an SNMP request, and if so, how are these
> attributes passed to access functions?
> Attributes include:
0) protocol (SNMP, AgentX, SMUX, internal callback, etc)
> 1) protocol type (v1, v2c, v3)
> 2) security model (comm(v1,v2c), usm, etc)
> 3) security level
> 4) security name
Yes - the attributes of the request probably do need to be
available to the MIB handling code (and I believe they are
with the v5 API). But the use of such attributes should
be avoided wherever possible, and the API documentation
probably needs to be splattered with warnings to that effect.
Dave
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
