hai, > > 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. >
I think it is reasonable to expect that a SET request for one context not to block any SET request for some other context. Can this be made available by default? > 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. > Where and how to modify? Can the control of whether to block some request for some table because of a SET request pending for some other table be given to the user level handler? I ask this since the tables can be totally unrelated and any type of request can go on in parallel for them? ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
