cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Hartle <mhar...@hartle-klug.com>
Subject Re: Cocoon 2.0 Scalability Disappointment
Date Sat, 01 Dec 2001 00:04:42 GMT
Peter Royal wrote:

>>>From a caching standpoint, I've removed everything dynamic out of my XSP 
>documents so the results are cacheable. (I still like XSP because I can 
>precompute static final java objects to stick in as Request attributes).
>
You can keep your XSPs dynamic and yet cachable when you are able to 
classify the parameters your XSP is based on and use them appropriately 
in the cache-relevant functions; some time ago, I mapped some URI space 
to a XSP page which in turn generated a JPEG navigation button via SVG; 
depending on what was entered in the path, the pictures and labels on 
the button changed. By using these parameters in cache key 
generation/validation functions in the XSP (not sure  how exactly, but 
the code is around somewhere), I got the individual results 
appropriately cached.

Best regards,

Michael Hartle



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message