SNMP Agent and Client in same process

Hey guys,

is it possible to have a snmp-agent and a client within the same process?

My application is requesting the uptime from other snmp servers and sends traps (e.g. it's own uptime). Right now I'm sending out my requests first and after that my traps, because that is not timecritical. 

Now I want to add the functionality that a client can request more information from my application. net-snmp says, that it should be only used within one thread (or multiple processes), but is it really necessary to protect the check_agent_and_process-method? If it is, I might run into problems.

Example: The app sends out an uptime request to a device, which is offline. Right after sending out the request, it gets one or several requests from one of its clients. 

Is it correct that because net-snmp is not threadsafe my app would have to wait until it gots the answer of its own request (in this case a timeout) before it can reply to the client request? That would be really a problem, even if I priorize the client requests, the app needs to wait for the outstanding requests.

I hope some of you guys can help me with my problem. Starting the snmp agent in an own process would be pretty bad for me, as my app runs as a service and it is planned that it should run with multiple instances in the future.
-- 
Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!  
Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users