Agent Modes - Revision history

Rstory: /* Set processing */

2010-06-22T17:55:13Z

‎Set processing

2008-10-15T20:38:17Z

‎Baby Steps

2007-10-15T15:40:45Z

@@ Line 11: / Line 11: @@
 == Set processing ==
 === SET_RESERVE1 ===
 The purpose of SET_RESERVE1 is to try and detect invalid SET requests
@@ Line 18: / Line 24: @@
 === SET_RESERVE2 ===
 The purpose of SET_RESERVE2 is to set up/allocate the data structure for a new
-row or perform any resource allocation needed for further processing (e.g. database locks).
+row or perform any resource allocation needed for further processing (e.g. allocate
 === SET_FREE ===
 The purpose of SET_FREE is to undo anything done in the two SET_RESERVE
 passes, if some aspect of the request proves unacceptable.   This means
-possibly releasing the data structure for a new row, if one has
+possibly releasing the data structure for a new row, if one was
-just been created.
+just been created. No action was performed, so no undo is needed.
 === SET_ACTION ===
@@ Line 39: / Line 46: @@
 === SET_COMMIT ===
 The purpose of SET_COMMIT is to confirm that the processing of the SET
-request has completed successfully, and perform any "irreversible" actions.
+request has completed successfully, and perform any "irreversible" actions. For
 == Baby Steps ==

@@ Line 43: / Line 43: @@
 == Baby Steps ==
-TBD
+see agent/helpers/baby_steps.c
 [[Category:Agent]]

@@ Line 1: / Line 1: @@
 {{GoodAnswer}}
-== Question ==
+= Question =
 What are the various modes that the agent goes through when answering requests.
-== Answer ==
+= Answer =
 == Get processing ==