[ http://issues.apache.org/jira/browse/FOR-711?page=comments#action_12365912 ]
Ross Gardler commented on FOR-711: ---------------------------------- Following on the AggregatedValidity trial (no idea how Cocoon caching works, so I'm just dumping ideas at present)... org.apache.cocoon.components.source.impl.MultiSourceValidity describes itself as: <p>An aggregated [EMAIL PROTECTED] SourceValidity} for multiple sources.</p> Now the question is, can an InputModule use these sitemap component cache tools - I'm guessing there is a reason the XMLFileInputModule doesn't use these classes... > Cache results from the Locationmap > ---------------------------------- > > Key: FOR-711 > URL: http://issues.apache.org/jira/browse/FOR-711 > Project: Forrest > Type: Sub-task > Components: Locationmap > Reporter: Ross Gardler > Priority: Critical > Fix For: 0.8-dev > > Now that we are using the locationmap extensively it is showing up just how > innefficient it is. The problem is that for the majority of requests there > are multiple reqeuests to the locationmap. We can make things much faster > (especially on the first page request) by caching results in the locationmap. > I think a simple cache will sufice, lets just provide a static hashmap using > the hint as a key and, of course, the location as the value. > If we test all locationmaps and find no result we should record that tere is > no result in this hashmap. This will also be a good place to throw an > exception so that Cocoon can better report such errors (see FOR-701) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
