Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Date: Mon, 9 Feb 2004 11:38:39 +0100
Subject: Re: [IMP] Release Showstoppers!
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
From: Bertrand Delacretaz <bdelacretaz@apache.org>
To: dev@cocoon.apache.org
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <53531E56-5AEB-11D8-A3A5-000A95A55C00@adolos.co.uk>
Message-Id: <1F893E40-5AEC-11D8-862C-000393CFE402@apache.org>

Le Lundi, 9 f=E9v 2004, =E0 11:32 Europe/Zurich, Stuart Roebuck a =E9crit =
:

> On 7 Feb 2004, at 2:36 pm, Geoff Howard wrote:
>
>> Vadim Gritsenko wrote:
>>
>>> Bertrand Delacretaz wrote:
>>>> Le Samedi, 7 f=E9v 2004, =E0 15:15 Europe/Zurich, Geoff Howard a =
=E9crit :
>>>>
>>>>> Vadim Gritsenko wrote:
>>>>>
>>>>>> 5) Cacheable XSP is *painfully* slow! It takes 2 seconds per=20
>>>>>> request!!!...
>>>>
>>>>> Um, isn't that because the xsp intentionally sleeps for 2 seconds=20=

>>>>> so you can observe the effect of the caching?  It says it is doing=20=

>>>>> so right on the page last time I looked.
>>>>
>>>> Indeed, this is by design so one can easily tell whether the page=20=

>>>> is served from the cache or generated.
>>> Good, then strike (5) from the list :-)
>>
>> As long as I can take credit for "fixing" it!
>>
>
> Am I missing something here. I thought that logging was there to=20
> enable this kind of 'debugging' with the absolute minimum of time=20
> penalty.  Using a two second delay in a production version as a=20
> 'hidden' way of communicating what's going on seems, to put it mildly,=20=

> 'daft'.

Depends if you call samples "production stuff".

This delay is coded in the cacheable.xsp page, which is a sample page,=20=

and does not affect the rest of Cocoon in any way.

And it is clearly written on the page that this is so, so it is not=20
hidden either. Maybe Vadim has seen the page so often that he didn't=20
read it this time ;-)

-Bertrand=