thread-local session list via an
opaque session pointer (a session list with a single session) instead
of using a global session list. Correct me if I am wrong on this one
(see link below) :
http://www.net-snmp.org/docs/README.thread.html
If you really use threads, why not a thread for each session
Den 21-07-2010 21:53, Brendan Tauras skrev:
> Now you're probably thinking why do asynchronous Single API requests.
> I have been tasked to write a snmp monitoring program. It must
> request different OIDs at different time intervals, and one request
> cannot hold up another (e.g. walks can take a
the opaque session pointer for subsequent calls. Since the callback
function is asynchronous and does not return to the original calling
code, the callback function is the only place that knows whether the
walk is finished or requires another (bulk) request.
Now you're probably thinking w
On 20 July 2010 17:54, Brendan Tauras 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.
>
Thank you for your help. I must be doing something wrong because 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. I have compile errors
If I use any other
On 20 July 2010 15:54, Brendan Tauras wrote:
> Is there a way to get the opaque session pointer (struct session_list
> * typecasted as a void *) from the regular session pointer (struct
> snmp_session *) when using the Single API?
I don't believe so, no.
If you're using the
Is there a way to get the opaque session pointer (struct session_list
* typecasted as a void *) from the regular session pointer (struct
snmp_session *) when using the Single API? Thanks. -Brendan
--
This SF.net email
