cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From da...@cocoon.zones.apache.org
Subject [DAISY] Updated: Introduction
Date Wed, 30 May 2007 21:11:46 GMT
A document has been updated:

http://cocoon.zones.apache.org/daisy/documentation/1372.html

Document ID: 1372
Branch: main
Language: default
Name: Introduction (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 5/30/07 9:11:29 PM
Updated by: Reinhard Pötz

A new version has been created, state: publish

Parts
=====

Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 1450 bytes (previous version: 37 bytes)
Content diff:
--- <html><body><p>TODO</p></body></html>
+++ <html>
+++ <body>
+++ 
+++ <p>Cocoon has advanced control flow, the ability to describe the order of Web
+++ pages that have to be sent to the client, at any given point in time in an
+++ application.</p>
+++ 
+++ <p>Traditional Web applications try to model the control flow of 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 into 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 between them grows as
+++ well, and it becomes hard to visualize what's happening in the application.</p>
+++ 
+++ <p>Moreover, the interactions in some applications are more complex than a
+++ simple finite state machine. In such cases it's much easier to think of and
+++ implement the application as a program, rather than a FSM.</p>
+++ 
+++ <p>By using a high level programming concept called <em>continuations</em>,
+++ Cocoon tries to solve this problem, and promises to allow the control flow in
+++ Web applications to be modeled as a normal program.</p>
+++ 
+++ </body>
+++ </html>


Mime
View raw message