On 20 July 2010 17:54, Brendan Tauras <[email protected]> wrote: > I am getting the internal snmp_session pointer from the Single API. > When I use snmp_sess_async_send(), my callback function gets > a snmp_session pointer instead of an opaque session pointer.
OK - I see where this is coming from. > Am I doing something wrong? No. You're probably seeing something of the history of the Net-SNMP development. The SSI approach was a later addition, with the traditional API re-worked as a wrapper around it. It looks as if the asynchronous callbacks still show something of the traditional parentage. I'm not really an expert on the SSI style of working (and unfortunately the person who did most of this work is no longer actively involved in the project). But my understanding is that the 'snmp_session' structure is meant to hold all of the "user-interesting" information, with the opaque session being for the internal housekeeping stuff. Let's turn the question around. What are you trying to do in the callback? Why do you need access to the opaque session structure? Dave ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
