> Gerhard Froehlich wrote:
>
> hi,
> I re-read the thread "Proposal for intermediate output stream".
>
> According to Carsten the approach would be a configurable intermediate
> pipline. That means for developing or testing you can use the
> intermediate
> pipline and for the production for example the cache pipeline.
>
> Configuration in the cocoon.xconf.
>
> Was that the result of the discussion?
>
This is the interesting question. There are two possibilities:
1) Make an own intermediate pipeline and use it as you mentioned above.
In that case you have to choose between the non caching, the
caching and the "intermediate" pipeline.
This implementation is simple but you can't use a "caching" intermediate
pipeline and in the whole sitemap this type of pipeline is used.
2) Extend the sitemap mechanism, e.g. with something like
<map:pipeline use-intermediate-output-stream="true">
<map:match pattern="...">
...
</map:match>
</map:pipeline>
Here you can choose which parts of the pipeline use the intermediate
outputstream and which ones not.
This is more flexible but all pipeline implementations (caching and
non caching) must take care of this special attributes.
I think it was Giacomo, who proposed a simmilar mechanism a while ago
for deciding if caching should be used inside a <map:pipeline> or not.
This would enable to cache only parts of your sitemap and not the
whole one.
As far as I remember the discussion, the solution 2) is the way to go.
Carsten
> Cheers
> Gerhard
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
