Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 25542 invoked by uid 500); 14 Apr 2003 13:46:34 -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 25527 invoked from network); 14 Apr 2003 13:46:33 -0000 Received: from pop016pub.verizon.net (HELO pop016.verizon.net) (206.46.170.173) by daedalus.apache.org with SMTP; 14 Apr 2003 13:46:33 -0000 Received: from verizon.net ([139.85.116.117]) by pop016.verizon.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP id <20030414134634.FOUF1833.pop016.verizon.net@verizon.net> for ; Mon, 14 Apr 2003 08:46:34 -0500 Message-ID: <3E9ABC3E.70107@verizon.net> Date: Mon, 14 Apr 2003 09:48:46 -0400 From: Vadim Gritsenko User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [RT] error-handling for "cocoon:" pipelines References: <3E95893D.6060509@anyware-tech.com> <3E958C44.6050801@verizon.net> <3E958D73.9070508@anyware-tech.com> <3E95904B.7090205@verizon.net> <20030412145147.GC3135@expresso.localdomain> In-Reply-To: <20030412145147.GC3135@expresso.localdomain> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at pop016.verizon.net from [139.85.116.117] at Mon, 14 Apr 2003 08:46:34 -0500 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Jeff Turner wrote: >On Thu, Apr 10, 2003 at 11:39:55AM -0400, Vadim Gritsenko wrote: >... > > >>I feel it's not good idea to have pipeline used in both ways - >>internally via cocoon protocol and externally. I think we have kind of >>consensus here saying that pipelines accessed by cocoon protocol should >>be internal-only="true". >> >> > >Eek - no!! > >A case study: the current Forrest sitemap makes heavy use of cocoon: >pipelines to define 'source' and 'intermediate' formats: > > - Requesting index.xml gives you the doc-v11 format XML > - Requesting body-index.xml gives you HTML for just the page body > - Requesting index.html gives you the whole page > Ok (I still remember cocoon-docs webapp). >These are neatly segregated into separate pipelines. Access to 'source' >and 'intermediate' pipelines can be disabled easily by switching >internal-only to "true". > Ok. >However, when debugging its really useful to have access to >cocoon:-generated XML, > Agree. > so currently internal-only is switched off. > Ok. >IMHO, visibility of cocoon: pipelines is something the user should be >able to decide. > Agree. >There are perfectly good reasons for keeping them >visible, and its very simple to hide them if necessary. > Ok. Now tell me, why "Eek - no!! "? And no to what? Vadim