Re: Perl SNMP doc update questions

[Simon L. <si...@li...>]

>>>>> "wh" == Wes Hardaker <wjh...@uc...> writes:
>>>>> On Mon, 20 Nov 2000 10:12:41 -0500, "G. S. Marzot" <ma...@ti...> said:
G> last bit of administravia - there is a Net::SNMP perl module out on
G> CPAN currently and there is already some level of confusion between
G> our SNMP module and that one. I expect that level to rise some...I
G> guess this is just fair warning seeing as its too late to change
G> the name again.  Ideally our perl SNMP module would be named
G> Net::SNMP but I don't see that happening either.

> True...  I hadn't thought of that naming conflict.  I think the
> other one is still being developed/maintained at least minimally too
> (Simon's right?).

To add to the confusion...

Net::SNMP is not my code.  It is a much cleaner rewrite by David
M. Town of an older version of mine (which doesn't really have a name
itself... most people call it SNMP_Session.pm).  We haven't tried to
merge the two or even keep them similar, so functionality has diverged
between the two.

Both David's and my code are being maintained, i.e. there are new
versions.

I think there are good reasons for the existence of both SNMP.pm and
Net::SNMP (my own code should probably be merged into David's).  Some
applications will always prefer a standalone version that doesn't
require the net-snmp library (until all systems come with net-snmp
preinstalled :-), others need the enhanced features that
net-snmp/SNMP.pm provide, such as excellent MIB support, good BER
encoding/decoding performance, SNMPv3 etc.

So I agree with Joe that SNMP.pm should not be renamed Net::SNMP and
also that there's a likely source of confusion between NET-SNMP's Perl
bindings and Net::SNMP, but I don't know what to do about it either.
-- 
Simon.