[pLog-svn] r6940 - plog/branches/lifetype-1.2/class/controller

jondaley at devel.lifetype.net jondaley at devel.lifetype.net
Wed Jan 6 13:48:19 EST 2010


Author: jondaley
Date: 2010-01-06 13:48:19 -0500 (Wed, 06 Jan 2010)
New Revision: 6940

Modified:
   plog/branches/lifetype-1.2/class/controller/controller.class.php
Log:
just commenting change - the # marks were messing up my syntax highlighting (broken php-mode in emacs apparently

Modified: plog/branches/lifetype-1.2/class/controller/controller.class.php
===================================================================
--- plog/branches/lifetype-1.2/class/controller/controller.class.php	2010-01-06 18:47:40 UTC (rev 6939)
+++ plog/branches/lifetype-1.2/class/controller/controller.class.php	2010-01-06 18:48:19 UTC (rev 6940)
@@ -47,13 +47,13 @@
      *
      * (according to http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/web-tier/web-tier5.html)
      *
-     * # The controller receives a POST from the client.
-     * # The controller creates an Action corresponding to the requested operation (as described in the previous section).
-     * # The controller calls the Action's perform method.
-     * perform calls a model business method.
-     * # The controller calls the screen flow manager to select the next view to display.
-     * # The screen flow manager determines the next view and returns its name to the controller.
-     * # The controller forwards the request to the templating service, which assembles and delivers the selected view to the client.
+     *  The controller receives a POST from the client.
+     *  The controller creates an Action corresponding to the requested operation (as described in the previous section).
+     *  The controller calls the Action's perform method.
+     *    perform calls a model business method.
+     *  The controller calls the screen flow manager to select the next view to display.
+     *  The screen flow manager determines the next view and returns its name to the controller.
+     *  The controller forwards the request to the templating service, which assembles and delivers the selected view to the client.
      * 
      * The Controller uses an action map file that maps action parameters to action classes. This is file is
      * nothing more than an associative PHP array where the key of the array is the value of the action



More information about the pLog-svn mailing list