On 10/09/2007, Senthil Nathan <[EMAIL PROTECTED]> wrote: > Can you explain the purpose of SET_RESERVE1 and SET-RESERVE2 > and SET_FREE and SET-COMMIT fro row status perspective.
The purpose of SET_RESERVE1 is to try and detect invalid SET requests as soon as possible. If any of the columns are assigned an impossible value (wrong type, or out-of-range, etc), then the request fails. That's true for all the columns of the table (RowStatus and the "data" rows). The purpose of SET_RESERVE2 is to set up the data structure for a new row - when triggered by a 'create' assignment to the RowStatus column. The purpose of SET_FREE is to undo anything done in the two SET_RESERVE passes, if some aspect of the request proves unacceptable. In this case, this means possibly releasing the data structure for a new row, if one has just been created. Then there are the two steps you didn't ask about: SET_ACTION assigns the appropriate column values to the data structure for this row (either the new structure created in the SET_RESERVE2 step, or an existing row structure). SET_UNDO reverses anything done in the two SET_RESERVE steps or SET_ACTION - called if some part of the SET_ACTION processing fails. This is similar to the SET_FREE processing, but also needs to reverse any newly assigned values. The purpose of SET_COMMIT is to confirm that the processing of the SET request has completed successfully, and perform any "irreversible" actions. In terms of RowStatus handling, this basically means deleting a row. Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
