cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Foster <jafos...@uwaterloo.ca>
Subject Re: [status & RT] design challenges
Date Fri, 05 Apr 2002 17:17:34 GMT
> The ability to nest one into the other allows something that is not
> possible today: since there are frameworks that are web-app focused and
> frameworks that are publishing-focues. Cocoon will do both *together*
> with seamless integration and elegant coherence.

This is an area that has the potential be awfully confusing to new users.  
One thing that might help would be to "place" Cocoon with respect to other 
web application frameworks.  I haven't used many frameworks (too much "roll 
my own" I guess), but from what I understand the following describes some 
of the alternatives:

WebObjects
- you code everything in a procedural language and the runtime handles 
"continuations"
- individual web pages don't really exist

ColdFusion
- doesn't know about web applications, so you roll your own using "state 
machine" approaches
- lets you create single pages with embedded scripting

ASP
- doesn't know about web applications, so you roll your own using "state 
machine" approaches
- lets you create single pages with embedded scripting

There have to be other alternatives out there that I don't know about.  To 
this we can add:

Cocoon
- you code your *logic* in a procedural language and the runtime handles 
"continuations"
- you code your *presentation* as individual web pages created using 
transformations and/or embedded scripting
- the logic can make use of the presentation, which in turn can continue 
the logic

In a simplistic description, Cocoon is the fusion of WebObjects and 
ColdFusion :)

Jason


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message