cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <stef...@apache.org>
Subject Re: [RT]: Merging Stream And Event Pipeline
Date Wed, 03 Apr 2002 13:35:34 GMT
Carsten Ziegeler wrote:
> 
> Hi,
> 
> just a short and simple RT for today:
> 
> What do you all think about merging the stream and the event pipeline
> into one single interface/object?
> This would make the system less complex and reduce lookups per request
> as well.

I agree, +1. I've been bugged by the existance of two transports since
the first time I saw it but not bugged enough to propose or implement a
change.

> The splitting into those two objects was done to help implementing the
> cocoon: protocol. But AFAIK everywhere always those two objects are
> used in combination, even in the SitemapSource class implementing the
> cocoon: protocol.
> 
> And as we want to make configurable pipelines for the next release,
> this would be easier to handle as well.

what do you mean by 'configurable pipelines'?
 
> I know this is an incompatible change, but I think this wouldn't hurt
> anybody as I never heart of someone really implementing these interfaces.

Agreed, these are very low level stuff.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message