From 2067d1a727e7eb5e5ffb40e967f3d1fc4c8a41b2 Mon Sep 17 00:00:00 2001 From: Derek Allard Date: Thu, 13 Nov 2008 22:59:24 +0000 Subject: Changing EOL style to LF --- user_guide/overview/appflow.html | 188 +++++++++++++++++++-------------------- 1 file changed, 94 insertions(+), 94 deletions(-) (limited to 'user_guide/overview/appflow.html') diff --git a/user_guide/overview/appflow.html b/user_guide/overview/appflow.html index 8850b63e3..cdc6ac205 100644 --- a/user_guide/overview/appflow.html +++ b/user_guide/overview/appflow.html @@ -1,95 +1,95 @@ - - - - - -Application Flow Chart : CodeIgniter User Guide - - - - - - - - - - - - - - - - - - - - - -
- - - - - -

CodeIgniter User Guide Version 1.7

-
- - - - - - - - - -
- - -
- - - -
- - -

Application Flow Chart

- -

The following graphic illustrates how data flows throughout the system:

- -
CodeIgniter application flow
- - -
    -
  1. The index.php serves as the front controller, initializing the base resources needed to run CodeIgniter.
    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. -
- - - - -
- - - - - - + + + + + +Application Flow Chart : CodeIgniter User Guide + + + + + + + + + + + + + + + + + + + + + +
+ + + + + +

CodeIgniter User Guide Version 1.7

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

Application Flow Chart

+ +

The following graphic illustrates how data flows throughout the system:

+ +
CodeIgniter application flow
+ + +
    +
  1. The index.php serves as the front controller, initializing the base resources needed to run CodeIgniter.
    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