Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 84345 invoked by uid 500); 23 May 2003 14:11:50 -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 84289 invoked from network); 23 May 2003 14:11:49 -0000 Received: from unknown (HELO mail.dff.local) (62.159.19.130) by daedalus.apache.org with SMTP; 23 May 2003 14:11:49 -0000 Received: from altair.dff.local ([172.16.2.8] helo=dff.st) by mail.dff.local with esmtp (Exim 3.35 #1) id 19JDGw-0002Tw-00 for cocoon-dev@xml.apache.org; Fri, 23 May 2003 16:11:50 +0200 Message-ID: <3ECE2CC4.7080607@dff.st> Date: Fri, 23 May 2003 16:14:28 +0200 From: Torsten Curdt User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: Backend cache invalidation References: <1E0CC447E59C974CA5C7160D2A2854EC097CB1@SJMEMXMB04.stjude.sjcrh.local> In-Reply-To: <1E0CC447E59C974CA5C7160D2A2854EC097CB1@SJMEMXMB04.stjude.sjcrh.local> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hunsberger, Peter wrote: > It seems to me that this must be a classic Cocoon problem, but I really > haven't found any discussion of it or how to solve it: Have you had a look at the DBPrism stuff? It has a such cache integration. [1] ...but I haven't tested this yet. Just seen the advertisements from Marcelo F. Ochoa from time to time ;) I think it is a good idea ...the only problem is the backend integration. -- Torsten [1] http://www.dbprism.com.ar/dbprism/doc/xdocs/Server.html