From dev-return-101026-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Tue Jan 13 18:04:32 2009 Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 27938 invoked from network); 13 Jan 2009 18:04:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Jan 2009 18:04:32 -0000 Received: (qmail 63105 invoked by uid 500); 13 Jan 2009 18:04:31 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 63060 invoked by uid 500); 13 Jan 2009 18:04:31 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 63051 invoked by uid 99); 13 Jan 2009 18:04:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jan 2009 10:04:30 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 13 Jan 2009 18:04:30 +0000 Received: (qmail 27739 invoked from network); 13 Jan 2009 18:04:09 -0000 Received: from localhost (HELO scrat-2.local) (127.0.0.1) by localhost with SMTP; 13 Jan 2009 18:04:09 -0000 Message-ID: <496CD798.5000704@apache.org> Date: Tue, 13 Jan 2009 19:04:08 +0100 From: Carsten Ziegeler User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; de; rv:1.8.1.19) Gecko/20081209 Lightning/0.9 Thunderbird/2.0.0.19 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [C3] Pipeline component event types References: <49520644.30108@gmail.com> <4955F707.4020705@apache.org> <200812271413.43183.andreas.pieber@schmutterer-partner.at> <4956B9B2.7050300@apache.org> <495725CD.9050809@indoqa.com> <49576FCD.60902@apache.org> <495775FC.6060606@indoqa.com> <4957E5CF.2090307@apache.org> <49691C70.6050205@tuffmail.com> <002e01c974af$bcb64350$3622c9f0$@spoerk@gmx.at> <496BADE1.1070300@tuffmail.com> <496C60FC.9040203@apache.org> <496C8B35.3060700@tuffmail.com> <496C8C84.6080002@tuffmail.com> <496CA061.3000700@apache.org> In-Reply-To: <496CA061.3000700@apache.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Reinhard Pötz write: >>> Agreed. How do you know what kind of wrapper do you need if you don't >>> know what kind of events components consume and produce? > > My assumption is that the developer that uses the pipeline knows what he > does. :) While this assumption *should* be true, we all know that in most cases it is not. So I fear many people will stumble across this problem. But I have one question: if we don't allow to mix different event types in a single pipeline (and I guess by event types we mean sax, dom, stax) why do we have a generic pipeline interface? Wouldn't it be better/easier to have a sax pipeline, a dom pipeline, a stax pipeline, perhaps sharing a common interface? Carsten -- Carsten Ziegeler cziegeler@apache.org