Yes, that's to say, only when client wants to do this deliberately.
Otherwise, the requests is one column after the other.
Dave, I'm asking this because I am using "snmpwalk" to send the requests,
so, is it true for the most nature case, my explanation is right? I have
tried using "snmpget" to ret
On 10 April 2011 16:46, Zimmer Hu wrote:
> Right, I took it for granted that the varbinds for "each requests" is for
> the columns of "each row". There may be holes in table so this may not be
> the case. Nevertheless, is this assertion true for the "full-filled" table
> (a varbind in one requests
Right, I took it for granted that the varbinds for "each requests" is for
the columns of "each row". There may be holes in table so this may not be
the case. Nevertheless, is this assertion true for the "full-filled" table
(a varbind in one requests list == a request ==a column in a row)?
On Sun,
On 9 April 2011 13:46, Zimmer Hu wrote:
> As to my understanding (and your hints),
> netsnmp_table_iterator_helper_handler goes through each row first; Then for
> each row, it stores each column data(data_context) in TI_REQUEST_CACHE;
Close - but not quite.
The iterator goes through each row of
