Author: jpic
Date: Mon Mar 3 00:42:23 2008
New Revision: 7475
Log:
- Closed and removed "delegate most high-level mechanisms to the router?", as
requested by Thomas Nunninger - who submitted the idea.
Modified:
experimental/MvcTools/design/design.txt
Modified: experimental/MvcTools/design/design.txt
==============================================================================
--- experimental/MvcTools/design/design.txt [iso-8859-1] (original)
+++ experimental/MvcTools/design/design.txt [iso-8859-1] Mon Mar 3 00:42:23
2008
@@ -263,40 +263,6 @@
}
}
-Delegate most of the high-level mechanisms to the router?
----------------------------------------------------------
-
-The following snippet shows the API calls necessary in the user's public
-script, in that case ::
-
- <?php
- $parser = new ezcMvcExampleRequestParser();
-
- $input = $parser->createInput();
-
- $router = new ezcMvcExampleRouter();
- $output = $router->run( $input );
-
- //$viewManager = $router->getViewManager( $output );
- $viewManager = new ezcMvcExampleViewManager();
-
- // Creates the response and sends it to the client.
- $viewManager->handle( $input, $output );
-
-Or even ::
-
- <?php
- $parser = new ezcMvcExampleRequestParser();
-
- $viewManager = new ezcMvcExampleViewManager()
-
- $router = new ezcMvcExampleRouter(
- $parser,
- $viewManager
- );
-
- $router->run();
-
Open issues
===========
@@ -319,6 +285,9 @@
Controllers have a method looking like : run( ezcMvcInput $input ) It's up to
the controller to figure it's action using $input.
+
+Special considerations
+======================
Shipping of example-implementations
-----------------------------------
--
svn-components mailing list
[email protected]
http://lists.ez.no/mailman/listinfo/svn-components
