Oh, well, it was worth a try. It seemed sensible because what is
sitting in the cache is the generated XML. It seems like whenever it
wants to rerun the XSP it will have to recompile it as well.
Could the whole thing be caused by a misconfiguration? I could send you
my httpd.conf if that will help.
Matt Sergeant wrote:
> On Tue, 19 Feb 2002, Andrew Parker wrote:
>
>
>>I noticed that the cache was saying that the XSP had not changed, and so
>>the script was not rerun. Although this is correct, in a sense, it
>>should run the script if data is being posted. So I did this to XSP.pm:
>>
>>--- XSP.pm.old Tue Feb 19 11:54:59 2002
>>+++ XSP.pm.new Tue Feb 19 11:58:37 2002
>>@@ -81,6 +81,7 @@
>> if (exists($cache->{$key})
>> && !$xml->has_changed($cache->{$key}{mtime})
>> && defined &{"${package}::handler"}
>>+ && !($r->method() eq 'POST') #want to rerun on a post
>> )
>> {
>>
>
> That's incorrect - it recompiles your XSP page on every POST request.
> Something fishier is going on I'm afraid.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
