From 35322b4e063ec8874c4412361b3ea7bc97532b8b Mon Sep 17 00:00:00 2001
From: carl <>
Date: Wed, 18 Jan 2006 17:13:49 +0000
Subject: a name bug in Modules

---
 demos/quickstart/protected/pages/Fundamentals/Modules.page | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

(limited to 'demos/quickstart/protected')

diff --git a/demos/quickstart/protected/pages/Fundamentals/Modules.page b/demos/quickstart/protected/pages/Fundamentals/Modules.page
index 3fe190fe..ebf4ac53 100644
--- a/demos/quickstart/protected/pages/Fundamentals/Modules.page
+++ b/demos/quickstart/protected/pages/Fundamentals/Modules.page
@@ -11,31 +11,31 @@ PRADO uses configurations to specify whether to load a module, load what kind of
 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. <a href="#custom">Custom modules</a> may be configured or developed to override or supplement these core modules.
 </p>
 
-<a name="request" />
+<a name="request"></a>
 <h2>Request Module</h2>
 <p>
 Request module represents provides storage and access scheme for user request sent via HTTP. User request data comes from several sources, including URL, post data, session data, cookie data, etc. These data can all be accessed via the request module. By default, PRADO uses <tt>THttpRequest</tt> as request module. The request module can be accessed via the <tt>Request</tt> property of application and controls.
 </p>
 
-<a name="response" />
+<a name="response"></a>
 <h2>Response Module</h2>
 <p>
 Response module implements the mechanism for sending output to client users. Response module may be configured to control how output are cached on the client side. It may also be used to send cookies back to the client side. By default, PRADO uses <tt>THttpResponse</tt> as response module. The response module can be accessed via the <tt>Response</tt> property of application and controls.
 </p>
 
-<a name="session" />
+<a name="session"></a>
 <h2>Session Module</h2>
 <p>
 Session module encapsulates the functionalities related with user session handling. Session module is automatically loaded when an application uses session. By default, PRADO uses <tt>THttpSession</tt> as session module, which is a simple wrapper of the session functions provided by PHP. The session module can be accessed via the <tt>Session</tt> property of application and controls.
 </p>
 
-<a name="error" />
+<a name="error"></a>
 <h2>Error Handler Module</h2>
 <p>
 Error handler module is used to capture and process all error conditions in an application. PRADO uses <tt>TErrorHandler</tt> as error handler module. It captures all PHP warnings, notices and exceptions, and displays in an appropriate form to end-users. The error handler module can be accessed via the <tt>ErrorHandler</tt> property of the application instance.
 </p>
 
-<a name="custom" />
+<a name="custom"></a>
 <h2>Custom Modules</h2>
 <p>
 PRADO is released with a few more modules besides the core ones. They include caching modules (<tt>TSqliteCache</tt> and <tt>TMemCache</tt>), user management module (<tt>TUserManager</tt>), authentication and authorization module (<tt>TAuthManager</tt>), etc.
-- 
cgit v1.2.3