forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ross Gardler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FOR-711) Cache results from the Locationmap
Date Fri, 10 Feb 2006 12:28:56 GMT
    [ http://issues.apache.org/jira/browse/FOR-711?page=comments#action_12365887 ] 

Ross Gardler commented on FOR-711:
----------------------------------

With respect to adding data to the cocoon store, maybe this will help:

"Some components like the DirectoryGenerator and the TraxTransformer rely on the validity
of other factors than just a template or a set of files.  These components often can't determine
the validity at setup time.  The solution is to use the AggregateValidity and more specifically
the DelayedAggregateValidity.  The aggregated validity object provides an interface for you
to add additional validity components inside and returns the result of the set (typically
if one validity object is undertermined or invalid the whole set is)."

(from http://cocoon.zones.apache.org/daisy/documentation/writing/690.html)

Not looked at the atual code yet though

> 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


Mime
View raw message