On Wed, 20 Sep 2006 15:59:20 +0100 Graeme wrote: GW> Excellent thanks. That will be fine while waiting for the data to be GW> updated. GW> However once get_first/get_next has finished, the table_handler is GW> called to return the data. GW> Should I copy the required row of data found in get_first/get_next (into GW> my_data_context?) so that when the table_handler is called it is GW> guaranteed to be still pointing to the data (i.e. I won't have GW> updated/deleted the row data in-between the end of 'xxx_get_next' and GW> the start of 'xxx_table_handler') - or have I missunderstood something?
Good point. I'm not an expert on the finer points of the iterator handler, since I never use it. I think the helper might have the functionality of saving data for each 'best match' found during the iteration, but I'm not sure and don't recall the API. Hopefully one of the experts will speak up on if/how this works.. Another approach would be caching all the data, but that might not be feasible if you have lots of data. And if you get into caching, there are better helpers which are more efficient than the iterator helper. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
