Return-Path: Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 86847 invoked from network); 26 Jul 2000 16:41:35 -0000 Received: from frankfurt.denic.de (HELO notes.denic.de) (194.246.96.101) by locus.apache.org with SMTP; 26 Jul 2000 16:41:35 -0000 Received: from denic.de ([192.168.0.187]) by notes.denic.de (Lotus Domino Version 5.0.2c (Intl)) with ESMTP id 2000072618411090:1089 ; Wed, 26 Jul 2000 18:41:10 +0200 Sender: ulim Message-ID: <397F154C.F3980F31@denic.de> Date: Wed, 26 Jul 2000 18:43:56 +0200 From: Ulrich Mayring Organization: DENIC eG X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12-32 i686) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-users@xml.apache.org Subject: Re: Cocoon and caching capabilities References: X-MIMETrack: Itemize by SMTP Server on notes/Denic(Version 5.0.2c (Intl)|08 Februar 2000) at 26.07.2000 18:41:10, Serialize by Router on notes/Denic(Version 5.0.2c (Intl)|08 Februar 2000) at 26.07.2000 18:41:24, Serialize complete at 26.07.2000 18:41:24 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Robin Green wrote: > > XSP incurs only a one-time overhead while the page is compiled [...] > By default, all XSP pages are assumed to have changed on every request, so > nothing more needs to be added! :-) This seems to be a contradiction. If all XSP pages are assumed to have changed on every request, then they would be compiled every time, not just the first time. My impression is, if an XSP hasn't changed, it is taken from the cache and executed again. If it has changed, then cocoon compiles it again. I thought that the hasChanged() method was introduced to tell cocoon the XSP page has changed, so it is compiled again. AFAIK non-XSP pages are never cached. If they indeed are, then please tell me where - at least in my repository there aren't any non-XSP files. Ulrich -- Ulrich Mayring DENIC eG, Systementwicklung