On Tue, 2005-08-30 at 12:14 -0400, Robert Story wrote:
> On Thu, 25 Aug 2005 09:27:19 +0100 Dave wrote:
> DS> I suspect that the easiest fix will be the same approach as for the
> DS> trap problem - have the AgentX master code explicitly append the
> DS> default port to the transport string (assuming there isn't one
> DS> there already, obviously!).
> Since you asked... maybe we need a new convenience function that deals with
> the new transport stuff and takes a parameter for a default, should one not be
> encountered in the specified string. This could be used in several places.
Yup - sounds good to me.
> It gets tricky, though. For example, trapsinks are defines as:
>
> trapsink HOST [COMMUNITY [PORT]]
>
> So, what if you get
>
> trapsink tcp:localhost:4321 public 1234
We'd clearly need to define which takes precedence.
In that particular case, I'd want to start deprecating the trailing-port
style, so I'd say that
trapsink tcp:localhost:4321 public 1234
and trapsink tcp:localhost:4321 public
should be regarded as equivalent.
But
trapsink tcp:localhost public 1234
and trapsink tcp:localhost:1234 public
should also be equivalent (for backward compatibility).
That would also probably be the simplest to implement.
(just passing these two fields to the new API call).
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
