cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <>
Subject RE: [RT]Cache/proxy friendly HTTP headers
Date Tue, 15 Jan 2002 07:06:00 GMT

Vadim Gritsenko wrote:
> ...
> *If* we are talking here about adding <map:parameter>s right after
> <map:pipeline> (as it was proposed in one of the messages)...
> First, you would need to extend implementation of pipelines with, say,
> Parameterizable interface. Then, you need to pass parameters from the
> sitemap to the pipeline. This could be done after line 660 in
> sitemap.xsl.
> This will work, but I'm not sure that this is the way to go...
> I think it's better to have ability to define pipeline configuration
> before actually using pipeline (somewhere under map:components),
> including what type of pipeline to use - caching, non-caching,
> profiling... I'm just not sure how to fit this with current sitemap
> implementation.

Yes, definitly. We could either change the configuration scheme already
available in the cocoon.xconf or follow your suggestion to place the
pipeline selection into the map:components part. I think, you're approach
is better as the pipelines belong to the sitemap.
So this is the first part we have to design. And then the parameters.


> > This rises another intersting question though: if we are heading to
> > different sitemap implementations (interpreted, compiled, scheme
> based)
> > it might be tricky to get all versions in sync when a new semantic is
> > added...
> The idea is to add new semantic rarely ;)
> Vadim
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, email:

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

View raw message