On 21/02/2008, Raghavendra Prasad <[EMAIL PROTECTED]> wrote: > A successful set operation will have the following sequence of switch > case calls > > MODE_SET_RESERVE1->MODE_SET_RESERVE2 > ->MODE_SET_ACTION->MODE_SET_COMMIT
Correct. > and a failed set operation will have the sequnce > > MODE_SET_RESERVE1->MODE_SET_RESERVE2 > ->MODE_SET_FREE->MODE_SET_UNDO No. There are several possibilities for a failed request: a) RESERVE1 (fail) -> FREE b) RESERVE1 -> RESERVE2 (fail) -> FREE b) RESERVE1 -> RESERVE2 -> ACTION (fail) -> UNDO > I was curious to know how this failure-sequence and sucess-sequence is > decided upon! The success sequence is designed to allow the MIB module coder the opportunity to handle multi-varbind SET requests reliably. The exact number or names of these stages are more-or-less arbitrary, but it's easy to show that a three-step approach is the minimum required. Our four-step model is inherited from the original CMU code, but there's an alternative, finer-grained approach described in the "baby-steps" helper. The varoius failure sequences follow on from this basic processing model. If either of the two RESERVE stages fail, then the FREE pass will be called. If the ACTION stage fails, then UNDO will be called. This is very similar to the AgentX SET processing model, though the names are different. Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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
