Vadim Gritsenko wrote:
>
> > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]]
> >
> > This would of course end up in a configuration nightmare. Another
> > possibility would be to make such a stream pipeline configurable in
> > the pipelines section of the sitemap:
> >
> > <map:pipeline name="caching">
> > <map:parameter name="expires" value="after 1 day"/>
> >
> > ....
> > </map:pipeline>
> >
> > So parameters would be passed on to the stream pipeline object which
> > could in turn set the corresponding http headers.
> >
> > What do think about this?
>
> How about this:
>
> <map:components>
> <map:pipelines default="caching">
> <map:pipeline name="caching">
> <stream-pipeline src="CachingStreamPipeline"/>
> <event-pipeline src="CachingEventPipeline"/>
> </pipeline>
> <map:pipeline name="profiling-caching">
> <stream-pipeline src="ProfilingCachingStreamPipeline"/>
> <event-pipeline src="ProfilingCachingEventPipeline"/>
> </map:pipeline>
> </map:pipelines>
> </map:components>
>
> <map:pipelines>
> <!-- note: type="" instead of name=""! -->
> <map:pipeline type="caching">
> <map:parameter name="expires" value="after 1 day"/>
> ....
> </map:pipeline>
> </map:pipelines>
>
> This would be more consistent with the rest of the sitemap.
Not really.
that's why we have <generator> and <generate>, 'actor' vs 'action'.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
