cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <>
Subject Re: Internal Pipelines (was: [RT] reconsidering pipeline semantics)
Date Thu, 04 Jul 2002 10:50:30 GMT
Carsten Ziegeler wrote:

>>-----Original Message-----
>>From: Sylvain Wallez []
>>Sent: Thursday, July 04, 2002 11:50 AM
>>Subject: Re: Internal Pipelines (was: [RT] reconsidering pipeline
>>Christian Haul wrote:
>>>I'm still trying to fully understand flow and the treeprocessor. I
>>>have the impression, that sending a page does not access internal-only
>>>pipelines. I found that sendPage uses a redirector to actually send
>>>the page in Any idea how this can be marked
>>>as an internal request?
>>The redirector used (ForwardRedirector) handles the special "cocoon:" 
>>protocol as internal redirects (aka "forward") which should consider the 
>>request as internal.
>>However, I noticed Carsten has added a processInternal() method to 
>>Processor and I wonder if there is some side-effects that break internal 
>>pipelines. Can you check if internal pilepelines still work as expected 
>>(using a simple cocoon: source) ? I unfortunately have no time to do it 


>>BTW, Carsten, I like very much this new processInternal() as it returns 
>>a pipeline object. This should make it very easy to implement pipeline 
>Actually this method is not so new at all. In former versions it was
>    boolean process(Environment environment, StreamPipeline pipeline,
>                    EventPipeline eventPipeline)

Yes, but with your change Processor handles the pipeline creation rather 
than accepting an existing one, and I think it's better this way.


Sylvain Wallez
  Anyware Technologies                  Apache Cocoon 

To unsubscribe, e-mail:
For additional commands, email:

View raw message