Hello Clint,
Yes, it is intended behaviour.
thank you for clarifying this.
What I do is keep all of my content in a single variable, and once
pretty much everything that could die has finished, I
$r->print($content) as the last action by my handler.
All the previous code is wrapped in an
On Jun 30, 2007, at 2:40 AM, Tony van der Hoff wrote:
Well, it is my intention that the modules should be reloaded if
they've
changed; that's the whole point of using Apache::Reload, so I'm
pleased it
works. Presumably, if they haven't changed, the only performance
hit is a
stat to the fi
Hi Christian
Yes, it is intended behaviour.
Basically, by the time that your script dies, it is too late to send the
correct headers to indicate a server error.
What I do is keep all of my content in a single variable, and once
pretty much everything that could die has finished, I
$r->print($con
Disclaimer: I have never used Apache::Reload, but:
Apache::Registry already looks for changes to your scripts and reloads
them as necessary. So you shouldn't need to use both of them. However,
reading the docs for Apache2::Reload, it mentions using it at the same
time as Registry scripts, which I
