The fourth parameter of an handler is netsnmp_request_info type. This appears as a list of requests, in fact there are 'next' and 'prev' field. Another field is 'netsnmp_variable_list *requestvb' that is a list of variable bindings.
I don't understand why there are two lists: requests (netsnmp_request_info type) and requestvb (netsnmp_variable_list type). In the delayed_instance.c example, there isn't any cycle: the only variable that is processed in MODE_GET case is requests->requestvb and stop. There isn't a check for the next variable (requestvb->next or requests->next). Instead, in agent/mibgroup/mibII/ip.c there is the following cycle in MODE_GET case: for (request=requests; request; request=request->next) but there isn't a cycle for requestvb list. When I register a custom scalar or a group of scalar, what should I write in the MODE_GET case (but also in MODE_SET and so on) in my custom handler? Are both the lists (requests and requests->requestvb) surely filled with only an element, or could be several elements to be processed in there? Should I implement one cycle or two nested cycles, or doesn't it matter? Thank you for the help. ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
