Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 68350 invoked from network); 25 Jan 2000 11:54:12 -0000 Received: from typhoon.mail.pipex.net (158.43.128.27) by 63.211.145.10 with SMTP; 25 Jan 2000 11:54:12 -0000 Received: (qmail 6378 invoked from network); 25 Jan 2000 11:54:10 -0000 Received: from userb669.uk.uudial.com (HELO picasso.o3.co.uk) (193.149.83.144) by smtp.dial.pipex.com with SMTP; 25 Jan 2000 11:54:10 -0000 Received: by picasso.o3.co.uk (Postfix, from userid 0) id AA95CD878; Tue, 25 Jan 2000 11:33:20 +0000 (GMT) Sender: mikew@picasso.o3.co.uk To: cocoon-dev@xml.apache.org Subject: Re: don't cache - validate References: <388C4C24.9C35B92@Haug.com> <20000124170735.I476@nc1a.nca.uea.ac.uk> <388C91F3.A86D384B@Haug.com> <20000124183207.M476@nc1a.nca.uea.ac.uk> From: Mike Williams Date: 25 Jan 2000 11:33:20 +0000 In-Reply-To: Paul Russell's message of "Mon, 24 Jan 2000 18:32:08 +0000" Message-ID: Lines: 13 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii >>> On Mon, 24 Jan 2000 18:32:08 +0000, >>> "Paul" == Paul Russell wrote: Paul> Sure, but shouldn't we be caching rather more than just the output Paul> (X)HTML? Translated XSPs, XSLs etc for a start. Yes! This makes a lot of sense where dealing with very dynamic content. Perhaps Cocoon2 should allow the admin to specify what points in the processing-chain are cachable? -- Mike Williams