PHPLights/Documentation/Global objects - Revision history

Nose: PHPLights/Documentation/Concepts moved to PHPLights/Documentation/Global objects: separated into subpages

2007-09-16T13:44:37Z

PHPLights/Documentation/Concepts moved to PHPLights/Documentation/Global objects: separated into subpages

Nose: moved front controller to own page

2007-09-16T13:40:42Z

moved front controller to own page

Nose: /* Global objects */

2007-09-12T20:05:57Z

‎Global objects

Nose: global objects

2007-09-03T21:25:27Z

global objects

Nose: /* Front Controller */

2007-09-03T20:52:47Z

‎Front Controller

Nose: /* Front Controller */

2007-09-02T16:11:19Z

‎Front Controller

Nose: front controller

2007-09-02T16:08:27Z

front controller

New page

== Front Controller ==

Applications based on PHPLights provide a single entry for all pages through their index.php file in the application directory. It starts up the library core which initializes the basic library components and sets up class autoloading.

Afterwards, the dispatcher forwards the request to the appropriate controller and action method. Controller, action and parameter are given via the URL, e.g.

index.php/default/index/2007/print

would specify the controller "default", the action "index" and the parameters "2007" and "print". The first two parameter after "index.php" are mapped the "index" method in the "DefaultController" class. All other parameter are available as numerically indexed array via the get() function of the request class:

LsContext::getRequest()->get('ls/param', <default>, <regex> );

Controller class and its methods must be implemented by the application and contains the business logic necessary to fulfill the request.

@@ Line 5: / Line 5: @@
 The context stores references to created objects during bootstrapping. This does include:
 * logging
 * request object
 * response object

← Older revision		Revision as of 21:25, 3 September 2007
Line 1:		Line 1:
		+	== Global objects ==
		+
		+	There are two objects which are available everywhere in the application: The context ([[PHPLights/API/LsContext\|LsContext]]) and the configuration ([[PHPLights/API/LsConfigIface\|LsConfig]]). Both are classes with static methods and don't need to be instantiated to be usable.
		+
		+	The context stores references to created objects during bootstrapping. This does include:
		+	* logging
		+	* configuration
		+	* request object
		+	* response object
		+	* database manager
		+	* user object
		+	* timer
		+
		+	The [[PHPLights/API/LsRequestIface\|request]] object provides access to the available parameters given by the server. It stores references to the GET, POST, REQUEST, ENV and SERVER variables. Using get() on the request object requires a regular expression which is used to check if the value which belongs to the key is what is expected by the application. Otherwise, a security exception is thrown.
		+
		+	The [[PHPLights/API/LsResponseIface\|response]] object is the opposite of the request object and it saves the prepared [[PHPLights/API/LsViewIface\|views]] until the output is finally generated by the dispatcher.
		+
		+	Authentication and access controll mechanisms are provided by the [[PHPLights/API/LsUserIface\|user]] object.
		+
		+	Finally, the [[PHPLights/API/LsTimer\|timer]] has invaluable information for performance optimizations. Each time the add() function is called, the time difference to the last call is stored and is available in the debug view.
		+
	== Front Controller ==		== Front Controller ==

@@ Line 10: / Line 10: @@
   $req = LsContext::getRequest()
-  $lst = $req->get('ls/param', array(), <regex> );
+  $list = $req->get('ls/param', array(), $regex );
 Controller class and its methods must be implemented by the application and contains the business logic necessary to fulfill the request.

← Older revision	Revision as of 13:44, 16 September 2007
(No difference)

@@ Line 19: / Line 19: @@
 Finally, the [[PHPLights/API/LsTimer|timer]] has invaluable information for performance optimizations. Each time the add() function is called, the time difference to the last call is stored and is available in the debug view.
-Applications based on PHPLights provide a single entry for all pages through their index.php file in the application directory. It starts up the library core which initializes the basic library components and sets up class autoloading.
+----
+Back to [[PHPLights/Documentation|Overview]]
-Afterwards, the dispatcher forwards the request to the appropriate controller and action method. Controller, action and parameter are given via the URL, e.g.
-−
- index.php/default/index/2007/print
-−
-would specify the controller "default", the action "index" and the parameters "2007" and "print". The first two parameter after "index.php" are mapped the "index" method in the "DefaultController" class. All other parameter are available as numerically indexed array via the get() function of the request class:
-−
- $req = LsContext::getRequest()
- $list = $req->get('ls/param', array(), $regex );
-−
-Controller class and its methods must be implemented by the application and contains the business logic necessary to fulfill the request.