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: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
