Some time ago, there was a brief discussion about what
operations were necessary for implementing and using
a table helper (regardless of the internal details
of exactly how that particular helper worked).
I've just submitted a revision to the container-based
table_data helper ('table_data2'), which includes a
first draft at just such a generic table API.
In broad terms, this falls into three main groups:
- a series of routines concerned with
creating and manipulating the table itself
(adding/removing rows, etc)
- a series of routines concerned with
*using* the information contained within
that table (retrieving particular rows, etc)
- a series of routines concerned with the
MIB interface to that table
(esp. relating to the 'request' parameter)
I'd be interested in hearing what people think about
this general framework. Is it missing anything obvious?
Fundamentally flawed? Generally OK?
Is it worth applying the same basic approach to some
(?all) of the other table helpers?
Dave
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
