> On 21/02/2008, ch k <[EMAIL PROTECTED]> wrote:
> > I ask you that your net snmp api is good than win
> snmp,
> > or winsnmp is good.
>
Dave Shield:
> But I'm not aware that any of us have done any
> significant
> work with the WinSNMP toolkit, so we're not really
> competent
> to comment on that one, or compare the two.
I've done client (manager-side) development with
WinSNMP and, when manager development was nearly
finished, I abandoned WinSNMP and took up with
Net-SNMP.
Why was that?
1. Unlike Net-SNMP, there is no WinSNMP development
going on; neither is there any support for WinSNMP.
2. Unlike Net-SNMP, WinSNMP does not support SNMPv3.
3. Net-SNMP is much more powerful, more accomodating,
and more flexible than WinSNMP.
4. WinSNMP source code is not available, which makes
diagnosing bugs a time-consuming and infuriating task.
5. WinSNMP documentation is complete, well organized,
and user friendly; it caters to my fundamental
laziness. Net-SNMP documentation sucks; it's a lot of
work to find my way around. That was the reason I
chose WinSNMP in the first place. But now that I've
used both packages, I see that the advantages of
Net-SNMP far outweigh this shortcoming.
Conclusion: for manager-side applications I will
choose Net-SNMP every time.
-- Pete Wilson
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
