>>>>> On Wed, 6 Jan 2010 12:11:48 -0500, Mike Gibson <[email protected]> >>>>> said:
MG> I have gone through the synchronous and asynchronous example applications on MG> the Net-SNMP site and see that they do both but don't seem to do both at the MG> same time. You need to use the asynchronous method to sending out the requests (with a call-back function to catch and process the responses). Then, don't use sleep or something to do the waiting. Instead use an snmp_alarm() registration to sleep for 10 seconds or so until the next "firing off" of the requests. In the mean time the responses will come back and get processed by the callbacks and eventually your alarm will get triggered to send out new ones. Note: you can't be 100% sure of the timing of the alarm if you're in the middle of processing other requests. IE, you may want exactly 10 seconds but if other requests are being processed at the time of the alarm and, say, they take 2 seconds to complete (I know; won't happen) then the alarm function will trigger at 12 instead. Your callback for processing won't get interrupted by the alarm. -- Wes Hardaker Please mail all replies to [email protected] ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
