cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Froehlich" <gerhard_froehl...@at.ibm.com>
Subject Re: [RT] reconsidering pipeline semantics
Date Wed, 03 Jul 2002 07:30:01 GMT

Stefano,

></skip>
>
>Composing pipelines
>-------------------
>
>Let me assume the above syntax gets introduced. At this
>point, we have four different ways to call a pipeline:
>
> - as a pipeline - as a generator - as a transformer - as a
>serializer
>
>let me write the code so you understand what I mean:
>
>[using a pipeline as a pipeline] (as today)
>
>   <pipeline>
>     <match pattern="*">
>       <call pipeline="blah"/>
>     </match>
>   </pipeline>
>
>nothing fancy here. Used mainly for verbosity reduction when
>the same pipeline is used in different places.
>
>[using a pipeline as a generator]
>
>   <pipeline>
>     <match pattern="*">
>       <call pipeline="blah"/>
>       <transform .../>
>       <serialize ../>
>       </match>
>   </pipeline>
>
>in this case, the 'serializer' of the called pipeline is not
>used and the output of the last tranformer of the named
>pipeline is connected with the input of the transformer
>right after the call.
>
>This is equivalent of *overloading* the serializer of the
>called pipeline with the rest of the pipeline in place.
>
>[using a pipeline as a transformer]
>
>   <pipeline>
>     <match pattern="*">
>       <generate ../>
>       <call pipeline="blah"/>
>       <serialize ../>
>      </match>
>   </pipeline>
>
>where both the generator and the serializer of the named
>pipeline are not used.
>
>This is equivalent of *overloading* both the generator and
>the serializer of the called pipeline with the rest of the
>pipeline in place.
>
>[using a pipeline as a serializer]
>
>   <pipeline>
>      <match pattern="*">
>        <generate ../>
>        <tranform ../>
>        <call pipeline="blah"/>
>      </match>
>   </pipeline>
>
>where the generator of the named pipeline is not used.
>
>This is equivalent of *overloading* the generator of the
>called pipeline with the rest of the pipeline in place.
>
></skip>

What are the typical use cases for:
(1) using a pipeline as a generator
(2) using a pipeline as a transformer
(3) using a pipeline as a serializer

?

Greets
Gerhard


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


Mime
View raw message