From 08b59ff62c4dfc98674c263269807798b6a83463 Mon Sep 17 00:00:00 2001 From: xue <> Date: Tue, 27 Dec 2005 01:46:50 +0000 Subject: --- .../protected/pages/Fundamentals/Modules.page | 37 ++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 demos/quickstart/protected/pages/Fundamentals/Modules.page (limited to 'demos/quickstart/protected/pages/Fundamentals/Modules.page') diff --git a/demos/quickstart/protected/pages/Fundamentals/Modules.page b/demos/quickstart/protected/pages/Fundamentals/Modules.page new file mode 100644 index 00000000..93573332 --- /dev/null +++ b/demos/quickstart/protected/pages/Fundamentals/Modules.page @@ -0,0 +1,37 @@ + + +

Modules

+

+A module is an instance of a class implementing the IModule interface. A module is commonly designed to provide specific functionality that may be plugged into a PRADO application and shared by all components in the application. +

+

+PRADO uses configurations to specify whether to load a module, load what kind of modules, and how to initialize the loaded modules. For more details, please see the configurations. +

+

+There are three core modules that are loaded by default whenever an application runs. They are request module, response module, and error handler module. In addition, session module is loaded when it is used in the application. PRADO provides default implementation for all these modules. +

+

+Developers may replace the core modules with their own implementations via application configuration, or they may write new modules to handle other tasks. For example, a module may be developed to provide common database logic for one or several pages. +

+ + +

Request Module

+

+

+ +
+

Response Module

+

+

+ +
+

Error Handler Module

+

+

+ +
+

Session Module

+

+

+ +
\ No newline at end of file -- cgit v1.2.3