On Fri, 9 Sep 2005 11:53:38 -0700 John wrote:
JM> Yeah, using semaphores/mutex's to lock access to the list is an option,
JM> but the intial thread safety design using the single session API seemed to
JM> intentionally avoid that. I suspect thats because sempahores/mutex's
JM> aren't well standardized across platforms (Win32...) and performance is
JM> better without them.
There is some support for multi-thread resource locking. See the mt_support
header and code, and grep for 'snmp_res_' in the code. Don't know the state of
the code, however. But it should server as a starting point.
--
NOTE: messages sent directly to me, instead of the lists, will be deleted
unless they are requests for paid consulting services.
Robert Story; NET-SNMP Junkie
Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders>
You are lost in a twisty maze of little standards, all different.
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
