Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 62149 invoked by uid 500); 27 May 2003 12:49:58 -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 62093 invoked from network); 27 May 2003 12:49:57 -0000 Received: from unknown (HELO host.leverageweb.com) (64.91.232.157) by daedalus.apache.org with SMTP; 27 May 2003 12:49:57 -0000 Received: from [134.205.205.162] (helo=WHEW00073U.leverageweb.com) by host.leverageweb.com with esmtp (Exim 3.36 #1) id 19Kdqq-00032m-00 for cocoon-dev@xml.apache.org; Tue, 27 May 2003 08:46:48 -0400 Message-Id: <5.2.0.9.0.20030527084806.02741018@leverageweb.com> X-Sender: cocoon@leverageweb.com@leverageweb.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 27 May 2003 08:49:19 -0400 To: cocoon-dev@xml.apache.org From: Geoff Howard Subject: RE: Backend cache invalidation In-Reply-To: <5.2.0.9.0.20030527075135.00a69cf8@leverageweb.com> References: <1E0CC447E59C974CA5C7160D2A2854EC0982E7@SJMEMXMB04.stjude.s jcrh.local> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.leverageweb.com X-AntiAbuse: Original Domain - xml.apache.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0] X-AntiAbuse: Sender Address Domain - leverageweb.com X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DOH! Not sure how I did it, but I forced my client to send the draft as well as a final version of this message. The full one is under a similar Subject with [proposal] prepended. Sorry. Geoff At 08:02 AM 5/27/2003, I wrote: >Ok, I looked at this over the weekend, and I have good news