Hi,I afraid this is a naive question but here it goes:I've fixed a lot of old CGI scripts over the past year and all new stuff to work in our MP2 environment and everything seems to be running excellent -- I mean GREAT, really.
We now use: SetHandler perl-script
I've fixed a lot of old CGI scripts over the past year and all new
stuff to work in our MP2 environment and everything seems to be
running excellent -- I mean GREAT, really.
Yes. I've never looked back myself. :)
If you're going all the way into modperl (arguably depending on your
needs), yo
Instead of using MP2 syntax, etc, we're still using:
print "Content-type: $type\n\n";
print "blah";
and in sending redirects, we use stuff like:
print "Location: $url\n\n";
Is this a problem or is it just bad style?
What reasons are there to continue our port to use the correct r
On Mon, 27 Mar 2006 14:08:38 +0100
"Carl Johnstone" <[EMAIL PROTECTED]> wrote:
> The next step from there is not using Apache::Registry at all, but
> putting mod_perl handlers into their own modules/packages. However
> there's more of a change here to other ways of working - for example
> you need
On Mar 27, 2006, at 9:42 AM, Frank Wiles wrote:
Overall great advice in this thread, but I wanted to point out
that with Apache2::Reload this isn't strictly the case. You can
set it to reload certain modules or all without a server restart,
however I personally wouldn't use it in produc
Thanks guys - this is helpful.In reality, and running the ways things are, I already need to restart (or ::Reload) to introduce changes (moved to that paradigm last year) -- but I guess that beyond the efficiencies you point out here in using proper API (for handler, print, etc) and the rationale h
Apache::Reload doesn't always work too. two scenarios
...
I use Apache2::Reload myself for my development box. There's an extra
scenario you missed out:
1. If you change the inheritance of the package, you'll get an error too.
But having said that, I find Apache2::Reload very handy for easy
On Mar 27, 2006, at 10:06 PM, Foo Ji-Haw wrote:
Apache::Reload doesn't always work too. two scenarios
...
I use Apache2::Reload myself for my development box. There's an
extra scenario you missed out:
1. If you change the inheritance of the package, you'll get an
error too.
But having
But having said that, I find Apache2::Reload very handy for easy and quick
development.
Me too!
Although I find that occasionally I have to restart apache on the
development box before it'll work correctly. Hence I wouldn't run it on a
production server.
Carl
