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 Thu, 01 May 2003 21:15:29 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-01 21:15 -------
Alex,

I don't think I get what you are trying to say about the .resource pipeline
wrongly claiming it is valid.

When I was debugging throught the AbstractCachingPipeline, I noticed that
(1) it first looks for cocoon:/test.resource to see if it is cached. 
(2) If it is, it used it. (3) If not it goes to the actual resource.
(4) It then looks for file://..../en.xml for example, (5) if that is cached,
it is used, (6) load it if not.

So, which one are you trying to say is invalid. It seems to me that trying
to look for a cached version at (1) should either be (a) turned off [no
cache for cocoon: type call, (b) or configurable to see what type of things
the key is dependent on, session attributes? request params? etc.

What do you think, Alex?

Boon

Mime
View raw message