Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3B294885.4040501@hartle-klug.com>
Date: Fri, 15 Jun 2001 01:28:05 +0200
From: Michael Hartle <mhartle@hartle-klug.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 0.8) Gecko/20010215
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Caching design issue
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hello all,

while having a deep look into Cocoon-2 for using it in commercial 
projects, I found 2 issues that robbed my sleep... ;)

- Using the <util:cacheable/>-tag suggests that an XSP page with this 
tag may be set up as cacheable; the stylesheet
org/apache/cocoon/components/language/markup/xsp/java/util.xsl turns 
this tag into a function called "isCacheable(Request)"; I used a 
brute-force grep over the whole source tree, but I could not find any 
call to this function, so it seems this is currently sort of deprecated.

- Using <map:match type="regexp" pattern="..."> and 
<map:parameter>-tags, I made an XSP-page which takes the parameters and 
generates SVG for navigational images, effectively turning a URI like 
/image/navigation/black/white/Cocoon%202.jpg into an JPEG image with a 
black "Cocoon 2" text on a white background; it worked perfectly, 
changing the colors or the text changes the resulting images. Sadly, the 
caching performance is nonexistant, as there is just one cached stream 
result per pipeline instead of one cached stream result per URL per 
pipeline; I am currently looking for easy ways to resolve this design 
issue and I would be happy to hear any ideas.

Best regards,

Michael


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