Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 80211 invoked by uid 500); 5 Apr 2002 21:02:27 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 80103 invoked from network); 5 Apr 2002 21:02:26 -0000 X-Antivirus-Data: Virus data file v4189 created Mar 06 2002 Message-ID: <3CAE10D4.2C07934@apache.org> Date: Fri, 05 Apr 2002 23:02:12 +0200 From: Stefano Mazzocchi X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [status & RT] design challenges References: <04C9F8E1-48B9-11D6-BD8B-000393567E34@uwaterloo.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Jason Foster wrote: > > > 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 :) It's much more than that, but I think it's a good explaination for people that are new to such complex systems. -- Stefano Mazzocchi One must still have chaos in oneself to be able to give birth to a dancing star. Friedrich Nietzsche -------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org