in reply to Re: mod_perl- am I safe?
in thread mod_perl- am I safe?

Thanks! My next step was to set up the virtual server, copy the database, and use ab (apache benchmark) to slam the server with requests and see what happens. Not very elegant, I suppose, but it should work well enough for testing.

I just wanted to know beforehand if I might be free and clear with mod_perl. I am using Apache::Registry as my mod_perl handler.

Here's the appropriate code from httpd.conf. I assume "UseStrict 1" helps protect variables? Sorry for what are probably basic questions, I'm figuring this stuff out gradually.

<Location /perl-bin>
        PerlSendHeader On
        SetHandler perl-script
        PerlHandler Apache::Registry
        PerlSetVar UseStrict 1
        Options +ExecCGI
</Location>

[download]

Replies are listed 'Best First'.
Re: Re: Re: mod_perl- am I safe?
by Masem (Monsignor) on Mar 23, 2001 at 20:35 UTC
    Don't have the docs handy, but OOTOMH, 'UseStrict' simply implies that use strict; would be at the top of every perl script that mod_perl handles, whether explicitly there or not. It doesn't protect any variables in any way. Of course, I will assume you already have use strict; at the top of every perl file you've written, don't you? :)

    Don't try to drop in the entire project at one shot; start with non-DB-destructive files like search routines or lookups, and make sure these work and apply any bug fixes that you need to across all project files. While it's a lot easier to build a site that will use mod_perl in an environment that already users mod_perl from scratch, existing scripts that use good perl programming practices should be able to drop in without any major gotchas, but there will always be a few.

    Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom