On Thu, Jan 6, 2011 at 3:55 PM, Wes Hardaker <[email protected]
> wrote:
>
> BV> CHANGES: agent: Added netsnmp_get_table_iterator2().
> BV> ...
>
> So... In general the newer handler things were created in a way that
> should be possible to not require new APIs to do things. IE, it should
> be possible to create new flags, etc, using the structures and
> extensibility mechanisms so we don't need new APIs.
>
> For the above, the only difference is:
>
> netsnmp_handler_owns_iterator_info(me) // me is the hanndler
>
> Now... To be honest I haven't followed all the code yet (it's early and
> I have a meeting in a few hours I need to prep for). So, where was the
> bug/issue/whatever that caused the need for a new API?
>
Hello Wes,
The difference is that when a table iterator created by a call to
netsnmp_register_table_iterator(reginfo, iinfo) is unregistered the memory
"iinfo" points at is not freed while unregistering a table iterator
registered by netsnmp_register_table_iterator2() does free that memory.
Bart.
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
