If I'm correct both Apache::PerlRun and Apache::Registry will have
problems in certain situations if we agree that ModPerl::Registry has
the correct logic for handling the execution status. If you can tell
otherwise please give me a test script that doesn't work under
ModPerl::Registry.
But in your particular example, Dick, if you configure the
I'm presuming that you simply mixed up which is my first name and
surname? :) Usually dave is fine. :)
script to run under Apache::RegistryNG, does it work?
No.
If not, that's where the difference between 1.0 and 2.0 lays:
ModPerl::Registry doesn't reset status if it wasn't changed by the
script.
well the ModPerl::Registry behaviour certainly suits my program. :)
Uru
-dave