On 21/09/06, Toth, Gregory S <[EMAIL PROTECTED]> wrote: > The void **my_loop_context appears to be a way to pass the current > position in the table (possibly an interator) from the > get_first_data_point method to the get_next_data_point method (and to > subsequent get_next_data_point calls) until the end of the table is > reached. It does not appear to be used by whatever calls the methods > in the module.
Exactly right. > It appears that it might not even be necessary to use the > **my_loop_context to do this. Simply declaring a global structure that > contains the index data (or an interator) then initializing it in the > get_first_data_point and updating it in the get_next_data_point appears > to work without even using the **my_loop_context variable. That would work currently, yes. It's probably not advisible, since such an approach would break if we ever managed to make the agent multi-threaded (opening up the possibility of two requests being processed in parallel. Dave ------------------------------------------------------------------------- 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
