You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Michael Melhem <mi...@fztig938.bank.dresdner.net> on 2002/08/12 17:14:28 UTC
Re: cachable readers (caching-point) fix
Hi Carsten (and other interested parties),
FYI, bugzilla [Bug 11633] simply moves up method: processReader(Environment
environment) into the common abstractCaching pipeline so that it can be
used by caching-point as well.
Caching-point plays no role when we have a pipeline size of 1, so we use
default caching pipeline behavior.
Best Regards,
Michael Melhem
Ps (Will now try to find the time to work on "pipeline-hint" stuff as
discussed with Sylvian Wallez and others :-P)
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: cachable readers (caching-point) fix
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Michael Melhem wrote:
> > >
> > > Ps (Will now try to find the time to work on "pipeline-hint" stuff as
> > > discussed with Sylvian Wallez and others :-P)
> > >
> > Hmm, personally I'm against these pipeline-hints as Cocoon should/can be
> > smart enough to handle everything automatically.
>
> Originally I was somewhat ambivalent about this issue, but can see
> some situations where manual cache hints might be useful.
>
> For example, there might be a particular pipleline where auto-caching
> might conceivably produce "too many" caching-points. One could fine-tune
> this situation by switching off auto mode, and use cache pipeline-hints
> selectively. However, I imagine this to be a very rare situation.
>
> Of course "pipeline-hints" is a generic proposal and is independent
> of the caching-point context.
>
>
> > But we can have a look
> > at this when it works and decide on the implementation then.
>
> When what works? Do you mean after the pipeline-hints works?
>
Sorry - yes when the pipeline-hints work (when you ;) implemented
them) - we can have a look at the implementation and the possible
scenarios and see if it makes sense or not.
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: cachable readers (caching-point) fix
Posted by Michael Melhem <mi...@fztig938.bank.dresdner.net>.
On Tue, Aug 13, 2002 at 11:25:48AM +0200, Carsten Ziegeler wrote:
> Michael Melhem wrote:
> >
> > Hi Carsten (and other interested parties),
> >
> > FYI, bugzilla [Bug 11633] simply moves up method:
> > processReader(Environment
> > environment) into the common abstractCaching pipeline so that it can be
> > used by caching-point as well.
> >
> > Caching-point plays no role when we have a pipeline size of 1, so we use
> > default caching pipeline behavior.
> >
> Thanks, I will apply this patch asap.
OK great!! :-)
>
> >
> > Ps (Will now try to find the time to work on "pipeline-hint" stuff as
> > discussed with Sylvian Wallez and others :-P)
> >
> Hmm, personally I'm against these pipeline-hints as Cocoon should/can be
> smart enough to handle everything automatically.
Originally I was somewhat ambivalent about this issue, but can see
some situations where manual cache hints might be useful.
For example, there might be a particular pipleline where auto-caching
might conceivably produce "too many" caching-points. One could fine-tune
this situation by switching off auto mode, and use cache pipeline-hints
selectively. However, I imagine this to be a very rare situation.
Of course "pipeline-hints" is a generic proposal and is independent
of the caching-point context.
> But we can have a look
> at this when it works and decide on the implementation then.
When what works? Do you mean after the pipeline-hints works?
>
> PS: I think Stefano wrote a good argumentation against these hints nearly
> one and a half year ago - but I might be wrong.
Not familair with this, Will need to look this up.
Regards,
Michael Melhem
>
> Carsten
>
> ---------------------------------------------------------------------
> 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: cachable readers (caching-point) fix
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Michael Melhem wrote:
>
> Hi Carsten (and other interested parties),
>
> FYI, bugzilla [Bug 11633] simply moves up method:
> processReader(Environment
> environment) into the common abstractCaching pipeline so that it can be
> used by caching-point as well.
>
> Caching-point plays no role when we have a pipeline size of 1, so we use
> default caching pipeline behavior.
>
Thanks, I will apply this patch asap.
>
> Ps (Will now try to find the time to work on "pipeline-hint" stuff as
> discussed with Sylvian Wallez and others :-P)
>
Hmm, personally I'm against these pipeline-hints as Cocoon should/can be
smart enough to handle everything automatically. But we can have a look
at this when it works and decide on the implementation then.
PS: I think Stefano wrote a good argumentation against these hints nearly
one and a half year ago - but I might be wrong.
Carsten
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org