ovidiu 02/04/26 00:01:08
Modified: src/scratchpad/schecoon/webapp/docs index.xml
Log:
Updated.
Revision Changes Path
1.4 +9 -7 xml-cocoon2/src/scratchpad/schecoon/webapp/docs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/src/scratchpad/schecoon/webapp/docs/index.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- index.xml 5 Apr 2002 20:33:50 -0000 1.3
+++ index.xml 26 Apr 2002 07:01:08 -0000 1.4
@@ -17,13 +17,15 @@
application.</p>
<p>Traditional Web applications try to model the control flow of
- a Web application by imagining the application as a finite state
- machine (FSM). For a client, the application can be only in one
- state at a time. Any request the client sends to the application
- makes it transition in a different state. As a side-effect of
- this transition, the application may update internal data,
- either in memory or in the database. The response to this
- transition is a Web page that's sent back to the client.</p>
+ a Web application by modeling the application as a finite state
+ machine (FSM). In this model, the Web application is composed of
+ multiple states, but the application can be only in one state at
+ a time. Any request received by the application transitions it
+ in a different state. During such a transition, the application
+ may perform various side-effects, such as updating objects
+ either in memory or in a database. Another important side-effect
+ of such a transition is that a Web page is sent back to the
+ client browser.</p>
<p>For simple Web applications, this model works fine. However,
as the application grows, the number of states and transitions
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
