Re: Handler: netsnmp_request_info parameter

2007-12-10 Thread Dave Shield
On 10/12/2007, Giuseppe Modugno <[EMAIL PROTECTED]> wrote: > Scalar helper is based on instance handler, so it is serialized too. > Is it correct? Err... probably, yes. > > > When I register a custom scalar or a group of scalar, what should I write > > > in > > > the MODE_GET case (but also in

Re: Handler: netsnmp_request_info parameter

2007-12-10 Thread Giuseppe Modugno
2007/12/10, Dave Shield <[EMAIL PROTECTED]>: > On 10/12/2007, Giuseppe Modugno <[EMAIL PROTECTED]> wrote: > > The fourth parameter of an handler is netsnmp_request_info type. > > This appears as a list of requests > > Correct. > This is the list of varbinds from the incoming request that are > rele

Re: Handler: netsnmp_request_info parameter

2007-12-10 Thread Dave Shield
On 10/12/2007, Giuseppe Modugno <[EMAIL PROTECTED]> wrote: > The fourth parameter of an handler is netsnmp_request_info type. > This appears as a list of requests Correct. This is the list of varbinds from the incoming request that are relevant to this particular handler. > Another field is 'net

Handler: netsnmp_request_info parameter

2007-12-10 Thread Giuseppe Modugno
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_re

Handler: netsnmp_request_info parameter

2007-12-10 Thread Giuseppe Modugno
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_re