>>>>> On Tue, 25 Oct 2005 17:52:41 +0530 (IST), madanagopal <[EMAIL PROTECTED]> >>>>> said:
madanagopal> If a SET request is pending in the agent, what other madanagopal> requests will be put on hold until that SET request is madanagopal> processed? Is it that requests for oids handled by madanagopal> handlers different from the one for that SET request will madanagopal> also put on hold? What about requests for other contexts? One set requests stops all other transactions from happening. Only GET/GETNEXT requests are allowed to happen in parallel. madanagopal> We want one SET request for one table not to block any madanagopal> other request for other tables for the same context. Also madanagopal> we want one SET request for any table for one context not madanagopal> to block any other request for any table for a different madanagopal> context. Is this possible or how to achieve this? You'd have to modify the code to achieve that. We don't do that by default, since predicting which tables are possible to modify and not mess up other tables is impossible to do generically. -- Wes Hardaker Sparta, Inc. ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
