David Crossley wrote:
Ross Gardler (JIRA) wrote:
Ross Gardler closed FOR-910.
----------------------------
Resolution: Fixed
Assignee: Ross Gardler
The resource is retrieved so often because it is needed to build the navigation
menus, which are on every page.
Yes, however it is still strange that there are so many requests.
There are only 33 html pages generated, yet 603 requests for doap.xml
So perhaps there is another issue with this "projectDetails" stuff.
Good point.
I didn't do any testing after my cache patch other than to look at the
time for site generation. Theoretically it should only be requested once
now.
The resource, when retrieved from the remote location is not cached efficiently
by Cocoon (I guess Cocoon does not check for validity of the remote file).
I fixed this by adding a cache to the pipeline that generates the site.ml
snippets from the DOAP files. The requests are cached for 10 minutes - should
be plenty of time for even a large site build - but this will cause problems if
trying to dynamically edit a DOAP.
Thanks, that is a good demo of using a bit more of the Cocoon cache
abilities.
We need to be careful about using it in a dynamic environment though, it
destroys the dynamic behaviour of edit and see results immediately.
I am not sure if this is related, but on a Cocoon app i use
a patch by Ugo Cei:
Re: Supporting "conditional GET" in Cocoon
http://thread.gmane.org/gmane.text.xml.cocoon.devel/59509
That looks like a useful addition. Maybe if I get the time I'll
resurrect the discussion about that patch [1] and get it applied to
Cocoon trunk. I don't want to apply it as the discussion you link to
seems to imply it should be improved upon.
In the meantime, I'm afraid there are more pressing things.
Ross
[1] https://issues.apache.org/jira/browse/COCOON-1726
