RE: clarification needed for net-snmp-5.2.1.2 mib2c.iterate.conf

Hi Dave,
Thanks for your speedy reply,
I am working with an application which will retrieve only row from the device at a time. So I am not able to load the entire table whenever the request comes. What I have understood after taking updTable as refrence that udpTable_load function is loading entire table during the query which is being dropped after a pre-defined time.
Thanks and Regards
./Shree Kant


-----Original Message-----
From: Dave Shield [mailto:[email protected]]
Sent: Tue 11/15/2005 2:33 PM
To: Shree Kant (WT01 - Broadband Networks)
Cc: [email protected]
Subject: Re: clarification needed for net-snmp-5.2.1.2 mib2c.iterate.conf
 
On Tue, 2005-11-15 at 12:11 +0530, [email protected] wrote:
>        I am using net-snmp-5.2.1.2 and used mib2c.iterate.conf to
> generate code, i don't want to load entire table into agents memory,

You don't need to - the iterator helper will quite happily
work through the table a row at a time, and only needs to hold
the information relating to a maximum of two rows.


>  I am planning to retrieve the data row by row and return the value

That's exactly how the iterator helper works, yes.

>  in this what i noticed is all GET-NEXT request is coming as GET
> request,

That's the whole *point* of the iterator helper.
*It* takes care of deciding which row is needed for a particular
incoming request (whether this is a GET or a GETNEXT request).
You don't need to worry about this - just report the appropriate
column from the row that's passed to the handler.

>  Is there any way to find whether the request is GET or GET-NEXT.

Why do you need to know this?

Dave