Dave Shield wrote:
Hold on - Robert suggested just *two* threads - one to receive the
requests and *one* to process them. A single worker thread - not multiple
threads. That means there's a single point where concurrency needs to be
handled - the queueing/dequeueing of requests on this "to-be-p
Hi Robert!
Robert Story (Coders) wrote:
1) A much more detailed analysis of all APIs in netsnmp is needed. The agent
uses lots of functions from the base snmplib. There are globals that will
need multi-threaded protection (the data-store stuff comes to mind).
That's defintely true, that has to be a
, the implementation.
Thanks,
Hermann Lacheiner
[1] http://caesar.ssw.uni-linz.ac.at/net-snmp-mt/mt-paper.pdf
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of
Hi coders!
I have written a short paper[1] that deals with multithreaded OID
handling. It discusses a few starting points.
I am looking forward to receiving your feedback and your help for
further steps, the implementation.
Thanks,
Hermann Lacheiner
[1] http://caesar.ssw.uni-linz.ac.at/net-snmp
Hi coders!
I'm digging into the multi-threaded handling of OID-handlers Daniel
Fallman wrote a few weeks ago. And to get faster into it I generated a
new doxygen (1.3.8) documentation for 5.2-pre1 with call graphs enabled.
I think it's very useful.
You can browse it on http://caesar.ssw.uni-linz.
