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 03:53:28 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 alex@romayev.com  2003-05-09 03:53 -------
Hi Boon,

I think there are two places where the change can take place.  

One is in FileGenerator, in which case, just like you said it would need to be 
configurable, similar to xslt transformer, e.g. <map:param name="use-request-
parameters" value="true"/> and <map:param name="use-session-attributes" 
value="true"/> or even something like <map:param name="use-session-attribute" 
value="locale"/>.

However, you can see how this could quickly get ugly.  I think the real issue 
is that when you're using cocoon: protocol, only the InputSource really knows 
its cache key.  So in FileGenerator:

    public java.io.Serializable getKey() {
        return this.inputSource.getURI();
    }

should be something like:

    public java.io.Serializable getKey() {
        return this.inputSource.getKey();
    }

Carsten (since looks like you're are the author of this code) are we on the 
right track here?

-Alex

Mime
View raw message