Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 85113 invoked by uid 500); 12 Mar 2003 07:41:55 -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 85096 invoked from network); 12 Mar 2003 07:41:54 -0000 Received: from mail.s-und-n.de (212.8.217.2) by daedalus.apache.org with SMTP; 12 Mar 2003 07:41:54 -0000 Received: from mail.s-und-n.de (localhost [127.0.0.1]) by mail2.s-und-n.de (postfix) with ESMTP id D4BF59FD8A for ; Wed, 12 Mar 2003 08:42:05 +0100 (CET) Received: from notes.sundn.de (ntsrv5.sundn.de [10.10.2.10]) by mail.s-und-n.de (postfix) with ESMTP id 488699FD88 for ; Wed, 12 Mar 2003 08:42:05 +0100 (CET) Received: from hw0386 ([10.10.2.66]) by notes.sundn.de (Lotus Domino Release 5.0.8) with SMTP id 2003031208420438:3802 ; Wed, 12 Mar 2003 08:42:04 +0100 From: "Carsten Ziegeler" To: Subject: RE: Encoding problems Date: Wed, 12 Mar 2003 08:42:36 +0100 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <3E6E6F83.7020201@hisitech.com> Importance: Normal X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 12.03.2003 08:42:04, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 12.03.2003 08:42:05, Serialize complete at 12.03.2003 08:42:05 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Santiago Gala wrote: > Re: cache comments later: > > When I was discussing Cocoon (then new) cache ideas with Ricardo > Rocha, (so around winter 2000/spring 2001) I sent an idea to Cocoon-dev > about propagating the CacheValidity to set the Expires in the seriazed > output. It looked like a clean (the only clean way I have found to date > in any famework) to set the "expires:" header in a web publishing > framework. AFAIK it got lost in the sea of bits. If any of you set on > fight against the cache, it could be very worthwhile. And I would have > contributed another bits to Cocoon ;-) > In theory it is possible to set the expires header and to propagate the cachevalidity. But (currently) the cachevalidity does not hold any expires information. In most cases it contains a last modification date of the used files (xml/xslt). Carsten