On Thu, 2005-05-05 at 21:09, Robert Story wrote: > On Thu, 05 May 2005 17:07:36 +0100 Dave wrote: > DS> I've come up with the following list of required tasks facing such > DS> a helper. What else (or different) would it need to provide? > DS> > DS> SNMP-request handling: > DS> - register (and unregister) the table > DS> - add or remove a row to/from the table > DS> - retrieve the row relating to a specific varbind request
> Actually, you may only need the index for the row. The handler > could deal with finding data for the index. Possibly - but again that feels more like "how" this particular API might be implemented, rather than removing the need for it altogether. (Plus this is included in the "External" list below) > Retrieving the next row. Ummm... Yes - that might be a sensible addition. It's probably not strictly necessary (since judicious use of "ASN_PRIV_RETRY" would have the same effect), and it might not be applicable to all table helpers (since many of them handle GetNext requests internally). But I can envisage situations where this might be useful. > Being able to pass in hints on requested columns would > be very helpful for sparse tables. > It might also be helpful to be able to find indexes/rows for > multiple varbinds. Both of those feel more concerned with the details of such APIs. I'm currently trying to concentrate on identifying the basic functionality that would be required for an arbitrary table helper. > DS> - retrieve the indexes relating to this row (?) > DS> > DS> External handling > DS> - retrieve a particular row (specified by index) > DS> - walk through the rows of the table (order not important) > > - adding/removing rows Covered above. > - finding a subset of rows (partial index matching) Yup - good idea. This could probably be regarded either as an extension of retrieving a particular (single) row, or a special case of walking (a subset of) the table. But that's a matter of detail again- the basic idea is a useful addition. > - retrieving rows based on other criteria besides table index Not convinced about this. I don't doubt that such a facility might well be useful, or even necessary for some tables. But it feels to fall outside the scope of a general "table helper API". Any such additional queries seem more a private matter for that particular table helper/implementation. Dave ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
