Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 87055 invoked from network); 18 Apr 2007 13:45:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Apr 2007 13:45:05 -0000 Received: (qmail 64046 invoked by uid 500); 18 Apr 2007 13:45:02 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 63979 invoked by uid 500); 18 Apr 2007 13:45:02 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 63956 invoked by uid 99); 18 Apr 2007 13:45:02 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Apr 2007 06:45:02 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [216.86.168.178] (HELO mxout-03.mxes.net) (216.86.168.178) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Apr 2007 06:44:53 -0700 Received: from [192.168.1.4] (unknown [87.206.142.101]) by smtp.mxes.net (Postfix) with ESMTP id 880BD5193C for ; Wed, 18 Apr 2007 09:44:32 -0400 (EDT) Message-ID: <462620A6.9040104@apache.org> Date: Wed, 18 Apr 2007 15:44:06 +0200 From: Grzegorz Kossakowski User-Agent: Thunderbird 1.5.0.10 (X11/20060911) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Cache global or per-servlet/per-sitemap? References: <46261492.3010000@apache.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Alexander Klimetschek napisaƂ(a): > Grzegorz Kossakowski schrieb: >> Thanks for investigating into it. Although I do not know much about >> cache internals it seems reasonable for me to have one cache per >> servlet, actually. As long as you don't use you have one >> sitemap per servlet so desired effect should be achieved. > > I think there are reasons for a global cache, probably the > implementation of the caches itself, as some save onto disk > (target/work/...) and they would need different directories each. After giving it more thinking I change my opinion. There are plenty of reasons to keep one, global cache. Otherwise, exactly the same resource would be cached several times in different blocks. -- Grzegorz Kossakowski http://reflectingonthevicissitudes.wordpress.com/