>>>>> On Mon, 12 Sep 2005 11:16:31 +0100, Dave Shield <[EMAIL PROTECTED]> said:
>> During init, defaults would be registered:
>>
>> netsnmp_yyy("snmpd:receive", "udp", "localhost", "161");
>> netsnmp_yyy("snmpd:agentx", "unix", "/var/agentx", NULL);
>> netsnmp_yyy("snmpd:trap", "udp", NULL, 0);
Dave> Hmmm...
Dave> I wasn't taken with this idea initially, but the more I think about
Dave> it (and the accompanying config directive), the more I like it.
Dave> I still suspect that a numberic serviceID might be more natural
Dave> for an application programmer, but the basic idea is a good one.
I actually agree with one of your earlier statements: (roughly) it
shouldn't increase complexity that much.
I do agree that we need the ability to specify default ports, but when
you look at exactly where that needs to be done where it's *not* the
norm then you'll see that's rather small. IE, currently only the trap
handling is unique in a default port number. The majority of the APIs
should be simple. open(SPEC); Deviating from that to require an app
to register something, then call another function with 4+ arguments in
order to do what 99% of the apps will likely do the same way doesn't
seem wise. Now, having said that, I have no issues having a wrapper
API do the above for the 99% case in order to improve flexibility for
the 1% case.
--
Wes Hardaker
Sparta, Inc.
-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
