>>>>> On Tue, 03 May 2005 16:43:59 +0100, Dave Shield <[EMAIL PROTECTED]> said:
Dave> /*
Dave> * NOTE NOTE NOTE: This helper isn't complete and is likely to
Dave> * change somewhat over time. Specifically, the way it stores
Dave> * data internally may change drastically.
Dave> */
Dave> *That's* probably why I thought it acceptable to start meddling
Dave> with the internals of these two helpers. But there doesn't seem
Dave> to be anything similar within the table_data code, and I'm not
Dave> sure how reasonable it is to enforce this warning anyway.
I'd argue we probably shouldn't enforce it... That'd be like changing
the AgentX internals and API because you've never taken it out of BETA
;-) (Ok, not quite comparable but it's close).
Dave> Which brings us back to the earlier question - what API calls
Dave> would be necessary for clean access to a dataset-style helper?
Dave> We've already got netsnmp_extract_table_row_data() to retrieve
Dave> a specific row, and assorted calls to locate a given column from
Dave> within a row. So I suspect we just need the same 'get_{first,next}'
Dave> calls in order to walk the table cleanly.
Dave> Does that sound about right?
Sure, though the row extraction one is only easily useful in a request
environment. Being able to extract rows based on a set of index
values would be useful, but more of a pain to implement.
--
Wes Hardaker
Sparta, Inc.
-------------------------------------------------------
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
