Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 32024 invoked by uid 500); 4 May 2003 12:13:17 -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 32011 invoked from network); 4 May 2003 12:13:16 -0000 Received: from grunt21.ihug.com.au (203.109.249.141) by daedalus.apache.org with SMTP; 4 May 2003 12:13:16 -0000 Received: from p216-apx1.syd.ihug.com.au (expresso.localdomain) [203.173.140.216] by grunt21.ihug.com.au with esmtp (Exim 3.35 #1 (Debian)) id 19CIMl-00042Q-00; Sun, 04 May 2003 22:13:16 +1000 Received: from jeff by expresso.localdomain with local (Exim 3.35 #1 (Debian)) id 19CINW-0003fK-00 for ; Sun, 04 May 2003 22:14:02 +1000 Date: Sun, 4 May 2003 22:14:02 +1000 From: Jeff Turner To: cocoon-dev@xml.apache.org Subject: Re: Making reloadability more fine-grained Message-ID: <20030504121402.GD3128@expresso.localdomain> Mail-Followup-To: cocoon-dev@xml.apache.org References: <20030504073737.GC3128@expresso.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.3i X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Sun, May 04, 2003 at 08:11:47AM -0400, Geoff Howard wrote: > Sounds fine to me, but would you use this on a live config? > I'd think no because of the overhead, in which case why not just allow > all reloads in your dev config and turn them all off on live? I think the performance impact is very minimal for those who forget to turn it off. The Source for cocoon.xconf is wrapped in a DelayedRefreshSourceWrapper, which means the lastModified() disk access is done at most once per second. --Jeff > > Geoff ...