diff options
| author | xue <> | 2005-12-27 01:46:50 +0000 |
|---|---|---|
| committer | xue <> | 2005-12-27 01:46:50 +0000 |
| commit | 08b59ff62c4dfc98674c263269807798b6a83463 (patch) | |
| tree | 4bb2dc445ad16d073ef9298f4a53dc568382c2b5 /demos | |
| parent | d06ae83d49bda2c8a4decd95f299776f1b6648aa (diff) | |
Diffstat (limited to 'demos')
3 files changed, 46 insertions, 1 deletions
diff --git a/demos/quickstart/protected/pages/Configurations/PageConfig.page b/demos/quickstart/protected/pages/Configurations/PageConfig.page index 7842e4f3..e6a6afaf 100644 --- a/demos/quickstart/protected/pages/Configurations/PageConfig.page +++ b/demos/quickstart/protected/pages/Configurations/PageConfig.page @@ -19,7 +19,7 @@ The format of a page configuration file is as follows, <module id="ModuleID" class="ModuleClass" PropertyName="PropertyValue" ... />
</modules>
<authorization>
- <allow pages="PageID1,PageID2" users="User1,User2" roles="Role1,Role2" verb="post" />
+ <allow pages="PageID1,PageID2" users="User1,User2" roles="Role1,Role2" verb="get" />
<deny pages="PageID1,PageID2" users="User1,User2" roles="Role1,Role2" verb="post" />
</authorization>
<pages PropertyName="PropertyValue" ...>
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 @@ +<com:TContent ID="body" >
+
+<h1>Modules</h1>
+<p>
+A module is an instance of a class implementing the <code>IModule</code> 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.
+</p>
+<p>
+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 <a href="?page=Configurations.Overview">configurations</a>.
+</p>
+<p>
+There are three core modules that are loaded by default whenever an application runs. They are <a href="#request">request module</a>, <a href="#response">response module</a>, and <a href="#error">error handler module</a>. In addition, <a href="#session">session module</a> is loaded when it is used in the application. PRADO provides default implementation for all these modules.
+</p>
+<p>
+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.
+</p>
+
+<a name="request" />
+<h2>Request Module</h2>
+<p>
+</p>
+
+<a name="response" />
+<h2>Response Module</h2>
+<p>
+</p>
+
+<a name="error" />
+<h2>Error Handler Module</h2>
+<p>
+</p>
+
+<a name="session" />
+<h2>Session Module</h2>
+<p>
+</p>
+
+</com:TContent>
\ No newline at end of file diff --git a/demos/quickstart/protected/pages/Fundamentals/Services.page b/demos/quickstart/protected/pages/Fundamentals/Services.page new file mode 100644 index 00000000..eabed42b --- /dev/null +++ b/demos/quickstart/protected/pages/Fundamentals/Services.page @@ -0,0 +1,8 @@ +<com:TContent ID="body" >
+
+<h1>Services</h1>
+<p>
+A service is ... TBD.
+</p>
+
+</com:TContent>
\ No newline at end of file |