| <?xml version="1.0"?> |
| <!DOCTYPE document [ |
| <!ENTITY project SYSTEM "project.xml"> |
| ]> |
| <document url="requestProcess.html"> |
| |
| &project; |
| |
| <properties> |
| <author email="yoavs@apache.org">Yoav Shapira</author> |
| <title>Request Process Flow</title> |
| </properties> |
| |
| <body> |
| |
| |
| <section name="Request Process Flow"> |
| |
| <p> |
| This page describes the process used by Tomcat to handle |
| an incoming request. This process is largely defined by |
| the Servlet Specification, which outlines the order |
| of events that must take place. |
| </p> |
| |
| <subsection name="description"> |
| <p> |
| TODO |
| </p> |
| </subsection> |
| |
| <subsection name="diagram"> |
| <p> |
| A UML sequence diagram of the request process is available |
| <a href="requestProcess/requestProcess.pdf">here.</a> |
| </p> |
| </subsection> |
| |
| <subsection name="comments"> |
| <p> |
| The Servlet Specification provides many opportunities for |
| listening in (using Listeners) or modiying (using Filters) |
| the request handling process even before the request arrives |
| at the servlet that will handle it. |
| </p> |
| |
| </subsection> |
| |
| </section> |
| |
| |
| </body> |
| </document> |
