From b0dd10f8171945e0c1f3527dd1e9d18b043e01a7 Mon Sep 17 00:00:00 2001 From: admin Date: Fri, 25 Aug 2006 17:25:49 +0000 Subject: Initial Import --- user_guide/overview/appflow.html | 101 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 101 insertions(+) create mode 100644 user_guide/overview/appflow.html (limited to 'user_guide/overview/appflow.html') diff --git a/user_guide/overview/appflow.html b/user_guide/overview/appflow.html new file mode 100644 index 000000000..0322a043e --- /dev/null +++ b/user_guide/overview/appflow.html @@ -0,0 +1,101 @@ + + + + +Code Igniter User Guide + + + + + + + + + + + + + + + + + + + + + + +
+ + + + + +

Code Igniter User Guide Version 1.4.0

+
+ + + + + + + + + +
+ + +
+ + + +
+ + +

Application Flow Chart

+ +

The following graphic illustrates how data flows throughout the system:

+ +
+ + +
    +
  1. The index.php serves as the front controller, initializing the base resources needed to run Code Igniter.
    2. +
  2. The Router examines the HTTP request to determine what should be done with it.
    3. +
  3. If a cache file exists, it is sent directly to the browser, bypassing the normal system execution.
    4. +
  4. Security. Before the application controller is loaded, the HTTP request and any user submitted data is filtered for security.
    5. +
  5. The Controller loads the model, core libraries, plugins, helpers, and any other resources needed to process the specific request.
    6. +
  6. The finalized View is rendered then sent to the web browser to be seen. If caching is enabled, the view is cached first so +that on subsequent requests it can be served.
    7. +
+ + + + +
+ + + + + + + \ No newline at end of file -- cgit v1.2.3-24-g4f1b