DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=25887>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=25887 [PATCH] Fix for caching of nested aggregations ------- Additional Comments From [EMAIL PROTECTED] 2004-03-17 13:32 ------- Don't know if it really makes sense :) Ok, smart-caching in 2.1.x is the way caching worked in 2.0.x. Now the new features is that if a cached response can't be found or is invalid, a shorter key is tried. So in this case, perhaps a partial cached response could be used as welll. However this decreases the processing time as the key is shortend and checked until the key is null (or something useful is found). Therefore you can configure it - of course as noone really knows about this option, noone uses it... Yes, I agree the name is a little bit confusing - unfortunately we can'T change it anymore :) Ok, I just tried the provided test case and it seems to work for me. I changed the internal pipeline calls to cocoon:/noaggregation and invoked the aggregationlevel3. Changing the directory causes all responses to be invalid and the response is created from scratch. What problem do you exactly experience?
