stas 2003/03/04 20:21:21
Modified: src/docs/2.0/user/handlers protocols.pod
Added: src/docs/2.0/user/handlers connection_cycle_time.dia
connection_cycle_time.gif connection_cycle_time.png
Log:
a new diagram
Revision Changes Path
1.6 +14 -1 modperl-docs/src/docs/2.0/user/handlers/protocols.pod
Index: protocols.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/handlers/protocols.pod,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- protocols.pod 4 Mar 2003 02:12:11 -0000 1.5
+++ protocols.pod 5 Mar 2003 04:21:21 -0000 1.6
@@ -32,7 +32,20 @@
can be also filtered though connection output filters. Filters are
usually used for modifying the data flowing though them, but can be
used for other purposes as well (e.g., logging interesting
-information).
+information). For example the following diagram shows the connection
+cycle mapped to the time scale:
+
+=for html
+<img src="connection_cycle_time.gif" width="599" height="300"
+ align="center" valign="middle" alt="connection cycle timing"><br><br>
+
+The arrows show the program control. In addition, the black-headed
+arrows also show the data flow. This diagram matches an interactive
+protocol, where a client send something to the server, the server
+filters the input, processes it and send it out through output
+filters. This cycle is repeated till the client or the server don't
+tell each other to go away or abort the connection. Before the cycle
+starts any registered pre_connection handlers are run.
Now let's discuss each of the C<PerlPreConnectionHandler> and
C<PerlProcessConnectionHandler> handlers in detail.
1.1
modperl-docs/src/docs/2.0/user/handlers/connection_cycle_time.dia
<<Binary file>>
1.1
modperl-docs/src/docs/2.0/user/handlers/connection_cycle_time.gif
<<Binary file>>
1.1
modperl-docs/src/docs/2.0/user/handlers/connection_cycle_time.png
<<Binary file>>
