Return-Path: 
 <users-return-53795-apmail-cocoon-users-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org
Received: (qmail 65641 invoked by uid 500); 4 Aug 2003 21:47:45 -0000
Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:users-help@cocoon.apache.org>
list-unsubscribe: <mailto:users-unsubscribe@cocoon.apache.org>
list-post: <mailto:users@cocoon.apache.org>
Reply-To: users@cocoon.apache.org
Delivered-To: mailing list users@cocoon.apache.org
Received: (qmail 65628 invoked from network); 4 Aug 2003 21:47:45 -0000
Received: from unknown (HELO host.leverageweb.com) (64.91.232.157)
  by daedalus.apache.org with SMTP; 4 Aug 2003 21:47:45 -0000
Received: from 66-44-62-116.s116.tnt5.lnhva.md.dialup.rcn.com ([66.44.62.116]
 helo=leverageweb.com)
	by host.leverageweb.com with asmtp (Exim 3.36 #1)
	id 19jn8U-0005Zy-00
	for users@cocoon.apache.org; Mon, 04 Aug 2003 17:44:58 -0400
Message-ID: <3F2EDA2D.4070608@leverageweb.com>
Date: Mon, 04 Aug 2003 18:11:57 -0400
From: Geoff Howard <cocoon@leverageweb.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: Caching of aggregate parts
References: <BB53DCD9.D2E2%lists@makeig.com>
In-Reply-To: <BB53DCD9.D2E2%lists@makeig.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse,
 please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.leverageweb.com
X-AntiAbuse: Original Domain - cocoon.apache.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - leverageweb.com
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Justin Makeig wrote:
> <map:match pattern="initiatives/*/">
>  <map:aggregate element="Page">
>    <map:part src="xml/toc.xml"/>
>    <map:part src="xml/site/initiatives/{1}.xml"/>
>   </map:aggregate>
>   <map:transform src="xsl/xhtml/initiatives/initiative.xsl">
>   <map:parameter name="requesturi" value="/initiatives/{1}/"/>
>  </map:transform>
>   <map:serialize type="xhtml"/>
> </map:match>
> 

This looks cacheable to me, unless I'm crazy and map:aggregate doesn't 
support caching  at all.  It should already be cached by default.  If 
you still have the samples running, check the status page and see if 
there is a pipeline key that looks like it matches.  It's not entirely 
clear, but you should be able to make some intelligent guesses.

Of course this may be bad news if you are not getting good performance 
from it.  If you turn logging all the way up to debug you should be able 
to see a processing time difference between its first request (after 
clearing the cache(s) or requesting with a new unique value of {1}

Geoff

>>Justin Makeig wrote:
>>
>>>I have a table of contents (TOC) document that is being aggregated with an
>>>XML instance document for each page request. For example, when
>>>http://mysite.com/Instance is requested, the sitemap aggregator generates a
>>>document that looks like:
>>>
>>><Page>
>>>    <TOC/>
>>>    <Instance/>
>>></Page>
>>>
>>>where TOC and Instance are loaded from the file system using
>>>map:aggreate/map:part.
>>>
>>>This system allows me to use XSL keys instead of the document function to
>>>reference elements in the TOC making the transforms speedy and cacheable.
>>>
>>>The TOC document is around 50K and growing arithmetically. Since the TOC is
>>>generated at design-time (not run-time), I would like to cache it so that it
>>>doesn't have to reparsed for every request. Is this possible? Is it already
>>>being done with map:aggregate? Any assistance would be much appreciated.
>>>
>>
>>Can you send your sitemap snippet that does the aggregation?
>>
>>Geoff


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