cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 17623] - Incorrect caching behaviour
Date Fri, 09 May 2003 15:29:57 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17623>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17623

Incorrect caching behaviour





------- Additional Comments From bhtek@yahoo.com  2003-05-09 15:29 -------
Hi Alex,

On the points you mentioned, I totally agree on (1) that it would get ugly
quick.

On point (2), it sure looks alluring to just shift the getKey to the input
source. However, my question is then how would the input source knows what
key to give you back? How does it know if it should take into account the
request parameter or any other criteria for that matter? What if we just
make sure anything called with a cocoon: protocol is not cached, and all we
just lose (as far as caching goes) should be just the step of going to the
actual file: part of the sitemap which is cached, one more redirection (I
think, Carsten?)

I was trying to debug the code without slowly reading it (bad Boon), but one
thing I noticed was that the file:'s getKey and getURI are called first before
the equiv for the cocoon:'s are called. I wonder how the flow really is but
it sure seems like if we make cocoon: never cached, we should not lose too
much.

Boon

Mime
View raw message