cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <joerg.heini...@gmx.de>
Subject Re: [SUMMARY] Caching DynamicSelectionList
Date Wed, 01 Jun 2005 16:37:37 GMT
Antonio Gallardo <agallardo <at> agssa.net> writes:

> > I don't think having a shorter cache period than a
> > form processing (as part of one request) makes no sense as it leads
> > to inconsistent forms when a selection list is reused.
> 
> Please explain. More this. Are you telling a cache life shorter than a
> request, makes or not makes sense?

Makes no sense. But not a request, only the processing phase of one form to be
exact.

> Sorry, for the above question. Too much negation on the sentence got me
> confused.

I like it  ;-)

> > Now I can think of optimizations of the above when you only use a
> > selection list (or the source it is based on to be exact) once in a
> > form: there is no need for buffering.
> 
> Yep. I told that in one of my first mails. It can also be stated as:
> caching matter only inside a repeater.

No, different selection lists might be based on one source. They must be equal
though.

> > Can this be determined?
> 
> Yep. If (the selection-list widget has not a repeater as ancestor) OR
> ((the selection list widget if has a repeater as ancestor) AND (the
> repeater has less than 2 rows)

No, see above (repeater is not sufficient). :-)

Joerg


Mime
View raw message