cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@sundn.de>
Subject AW: [C2]: Problems with content aggregation and redirects
Date Mon, 25 Jun 2001 06:13:45 GMT
> Giacomo Pati wrote:
> 
> On Fri, 22 Jun 2001, Carsten Ziegeler wrote:
> 
> > > Michael Hartle wrote:
> > >
> > > Carsten Ziegeler wrote:
> > >
> > > > The CA example doesn't work as the aggregated part
> > > (moreover/moreover.xml)
> > > > has no EventPipeline (it's a redirect).
> > > >
> > > > I think we should fix this. The easiest solution for this would
> > > be to make
> > > > the cocoon: url work and use them from inside the
> > > ContentAggregator as well.
> > > >
> > > > What do you think?
> > >
> > > Will the cocoon: protocol then later be used as the only way for to
> > > specifiy the source of an aggregation
> > > element ? If it is not so, then there would be two ways how 
> aggregations
> > > can be used (with or without the
> > > cocoon: protocol) and this counter-intuitive issue regarding sitemap
> > > redirects that are not being resolved
> > > would remain.
> > >
> > Yes, I personally would suggest that it is required to use the cocoon:
> > protocol. But I think we have to vote on this.
> 
> The sitemap aggregation was made exactly for aggregating cocoon
> pipelines because it aggregates XMLProducers not byte streams. I think
> aggregating other stuff is better suited by the xinclude transformer.
> 
Ok, the CA was made to aggregate pipelines, but what about aggregation
different "xml sources" which could either be pipelines but also completly
different urls. 
When (not if!) we have the cocoon: url the CA can do both of the above
without any change. And the great advantage over the xinclude transformer
is caching as CA is cacheable and the xinclude not.

Carsten

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

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


Mime
View raw message