Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of ap-cocoon-users@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: users@cocoon.apache.org
From: Jorg Heymans <jh@domek.be>
Subject: Re: Caching mysteries
Date: Wed, 31 Aug 2005 12:25:34 +0200
Lines: 34
Message-ID: <df40ir$h6n$1@sea.gmane.org>
References: <43130099.8010203@cs.uu.nl> <dev0j1$nr$1@sea.gmane.org>
 <43157A1D.8050201@cs.uu.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
In-Reply-To: <43157A1D.8050201@cs.uu.nl>
Sender: news <news@sea.gmane.org>


Sandor Spruit wrote:
> 
> Folks,
> 
> I am trying to speed-up my app (a search engine) by using caching. The idea
> is to to run a query once, and allow quick browsing through multiple
> pages of
> results without redoing the query - which is an expensive processing
> step. It
> does not seem to work as expected, in a way I do not understand! :-(
> 
Caching with aggregated has come up numerous times [1], maybe one those
threads gives you a clue.

Otherwise, the logs are pretty good in finding out exactly which
component thinks it should not deliver cached content.

Also, try setting up your sitemap outside of flow and aggregate it with
a static file to isolate the problem ie

<map:match pattern="test">
   <map:aggregate>
      <map:part src="mytest.xml"/>
      <map:part src="cocoon:/query"/>
   </map:aggregate>
</map:match>


HTH
Jorg

[1]
http://marc.theaimsgroup.com/?l=xml-cocoon-users&w=2&r=1&s=caching+aggregated&q=b


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