You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Vadim Gritsenko <vg...@hns.com> on 2001/07/05 16:06:35 UTC
ContentAggregation and caching
Carsten,
After you added "cocoon:" protocol, caching does not work anymore for
aggregated pipelines. Do you have any plans on reviving this feature?
Thanks,
Vadim
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: ContentAggregation and caching
Posted by Carsten Ziegeler <cz...@sundn.de>.
> -----Ursprungliche Nachricht-----
> Von: maciejka@tiger.com.pl [mailto:maciejka@tiger.com.pl]
> Gesendet: Freitag, 6. Juli 2001 17:02
> An: cocoon-dev@xml.apache.org
> Betreff: Re: AW: ContentAggregation and caching
>
>
> On 5 Jul 2001, at 16:14, Carsten Ziegeler wrote:
>
> > > Vadim Gritsenko wrote:
> > >
> > > Carsten,
> > >
> > > After you added "cocoon:" protocol, caching does not work anymore for
> > > aggregated pipelines. Do you have any plans on reviving this feature?
> > >
> > Yes, of course - but unfortunately time is currently very limited.
> > So if someone else wants to go with this...
> >
> > Here is my suggestion for a working solution:
> >
> > >>
> > For making this work the only change should be to the
> CocoonSourceFactory.
> > This must only calculate a valid last modification date for the
> > whole pipeline.
> > As this is a EventPipeline the last modification date can only be
> > available/valid if the whole pipeline is cacheable.
> > The last modification could then be fetched from the time the
> > response of this eventpipeline was put into the cache.
> > <<
> >
>
> Does it mean than CachedEventObject should be extended to contain
> time the eventpipeline has been put into the cache?
>
Yes, I think so. You could then simply see when it was put into the
cache and calculate the last modification date out if (or take this
as the last mod date.)
Carsten
>
> Maciek Kaminski
> maciejka@tiger.com.pl
>
> ---------------------------------------------------------------------
> 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
Re: AW: ContentAggregation and caching
Posted by ma...@tiger.com.pl.
On 5 Jul 2001, at 16:14, Carsten Ziegeler wrote:
> > Vadim Gritsenko wrote:
> >
> > Carsten,
> >
> > After you added "cocoon:" protocol, caching does not work anymore for
> > aggregated pipelines. Do you have any plans on reviving this feature?
> >
> Yes, of course - but unfortunately time is currently very limited.
> So if someone else wants to go with this...
>
> Here is my suggestion for a working solution:
>
> >>
> For making this work the only change should be to the CocoonSourceFactory.
> This must only calculate a valid last modification date for the
> whole pipeline.
> As this is a EventPipeline the last modification date can only be
> available/valid if the whole pipeline is cacheable.
> The last modification could then be fetched from the time the
> response of this eventpipeline was put into the cache.
> <<
>
Does it mean than CachedEventObject should be extended to contain
time the eventpipeline has been put into the cache?
Maciek Kaminski
maciejka@tiger.com.pl
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: ContentAggregation and caching
Posted by Carsten Ziegeler <cz...@sundn.de>.
> Vadim Gritsenko wrote:
>
> Carsten,
>
> After you added "cocoon:" protocol, caching does not work anymore for
> aggregated pipelines. Do you have any plans on reviving this feature?
>
Yes, of course - but unfortunately time is currently very limited.
So if someone else wants to go with this...
Here is my suggestion for a working solution:
>>
For making this work the only change should be to the CocoonSourceFactory.
This must only calculate a valid last modification date for the
whole pipeline.
As this is a EventPipeline the last modification date can only be
available/valid if the whole pipeline is cacheable.
The last modification could then be fetched from the time the
response of this eventpipeline was put into the cache.
<<
> Thanks,
> Vadim
>
> ---------------------------------------------------------------------
> 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