Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 92580 invoked by uid 500); 11 Jan 2002 10:48:35 -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 92560 invoked from network); 11 Jan 2002 10:48:35 -0000 Date: Fri, 11 Jan 2002 11:48:43 +0100 (CET) From: Torsten Curdt X-X-Sender: To: Subject: RE: [RT]Cache/proxy friendly HTTP headers In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N [snip] > This would of course end up in a configuration nightmare. Another > possibility would be to make such a stream pipeline configurable in > the pipelines section of the sitemap: > > > > > .... > > > So parameters would be passed on to the stream pipeline object which > could in turn set the corresponding http headers. > > What do think about this? I like that -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org