Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Message-ID: <3FE5C2DA.1090201@domek.be>
Date: Sun, 21 Dec 2003 16:57:14 +0100
From: Jorg Heymans <jh@domek.be>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.6b) Gecko/20031205 Thunderbird/0.4
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: problem with caching aggregated src
References: <20031220211905.1a974235.ruf10@op.pl>	<3FE4B2A8.1050705@domek.be>
	<20031220215213.2118a539.ruf10@op.pl>	<3FE4C2ED.8040309@domek.be>
	<20031220231339.0eac5e60.ruf10@op.pl>	<3FE4D361.6010209@domek.be>
	<20031221004235.40b5ad45.ruf10@op.pl>	<3FE5839C.7080706@domek.be>
	<20031221135603.6a38ad49.ruf10@op.pl>	<3FE5AC35.9050709@domek.be>
 <20031221160027.51268d23.ruf10@op.pl>
In-Reply-To: <20031221160027.51268d23.ruf10@op.pl>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Please file it as a bug in bugzilla, it might just be something wierd 
going on.

Question is do you really need caching? I mean how many hits/sec do you 
really expect from this in a live environment?

Another workaround would could be to touch the stylesheet after a 
fileupdate in src/main, this should invalidate the caching key and 
trigger a full pipeline reload.

jorg

rufio wrote:

> on Sun, 21 Dec 2003 15:20:37 +0100 Jorg Heymans <jh@domek.be> wrote:
> 
> 
>>ok so :
>>
>>1) test1.html -> caches
>>2) you add a file to src/main and request test1.html -> new file does 
>>not show up
>>3) you request test2.html -> new file shows up and is cached
>>
>>Is this what you're getting now?
> 
> 
> Exactly it's like this:
> I have some xml files in src/main, eg file1.xml and file2.xml, and all of them
> show up when I call any page as a menu. Now:
> 1) request file1.html -> file1.xml + all as a menu
> 2) add new.xml to src/main
> 3) refresh file1.html -> nothing happens
> 3) request file2.html -> see new menu with new.html
> 
> 
> 
>>Note that you can also set map:pipeline type="noncaching", try setting 
>>this. It's suboptimal but unless you're on a high traffic site you could 
>>live with it.
> 
> 
> Now it's ok.
> It's a development environment :) but what if it was production?
> 
> Regards, Rufio

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