Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Message-ID: <3A226AC4.5080104@veritas.com>
Date: Mon, 27 Nov 2000 09:08:04 -0500
From: Andy Lewis <andy.lewis@veritas.com>
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.12-20smp i686; en-US;
 m18) Gecko/20001010
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: [RT] Cocoon in cacheland
References: <39FEE6AA.107B9EED@apache.org> <3A1EF98C.C166C49E@apache.org>
 <3A2249A7.D7C1259B@anyware-tech.com> <3A2257DF.1D32E91C@ibuildings.nl>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

I'm basically a lurker now, but have used Cocoon 1.3 through 1.8 and 
anxiously await Cocoon 2. For what it is worth, Caching is a MUST. In 
fact, I was rather fond of the discussion that originated from Stefano 
that prposed a chache a virtully every step of the pipeline. This allows 
ony the changed elements of a complex output to be rebuilt.

Peter Verhage wrote:

> Sylvain Wallez wrote:
> 
>> Don't be sarcastic : cacheing is a *must have* if Cocoon wants to be
>> able to compare in terms of speed with other technologies (JSP, PHP and
>> others). The lack of response on this subject is probably caused by the
>> current stage of C2 : features are still being defined. As optimization
>> is not directly visible to the Cocoon user, it's not the main concern
>> today... but it will be as soon as C2 will be used in production
>> environments.
> 
> I agree. Cache is a must-have, because without caching Cocoon ain't that
> fast...
> 
> Peter
>