Re: I hate the net-snmp library

[Jamshed Kakar]

Hi,

> http://net-snmp.sourceforge.net/tutorial/toolkit/demoapp/index.html

Ew.  That was ugly.

> I'm thinking of a nice starting set of wrappers:
> 
> try {
> snmp_connection foo = new snmpv1_connection("server", "community");
> } catch { // Various can't connect errors;
> }

What exactly would this do?  Or what would you do once you had the
connection?

What kind of things do we need to represent?  I'm assuming some kind
of device hierarchy- in fact, you could probably build a map of the
network using a composite tree.  This is potentially a bad solution if
you intend to have lots of different interfaces to devices.  At this
point my assumption has been that a generic interface to devices will
have to be created.

> I'm not sure yet how to handle an snmpwalk type of sequence, but I
> think I'd like it to be something like it either returning a list<pdu
> *>, or something.  Suggestions?

Building out the composite tree would be easy to cook up quickly if
nothing else.  A tree is also much more descriptive than a list.  If
you intend to keep these structures for a long time AND want to view
the data in a particular way it wouldn't be hard to build observers to
watch changes in the tree and update indexes.

Take care,
Jamu.

-- 
 Premature optimization is the root of all evil. -- Donald Knuth