The problem is that you really can't have a "shared"
mod_perl if you don't trust who you are sharing it with.
For example, I could execute the following code in my
module:
BEGIN {
*strict::import = sub { die "ho ho ho" }
}
And now your code when it loads with the nearly-required
use strict will execute
my trojan horse.
There's no real way to protect against that. One shared persistent interpreter is one shared persistent interpreter.
You can run mod_perl in the "virtual host" solutions where each user has a completely independent Apache process group, sharing only the CPU.
But don't count on a mod_perl solution where you and others are all sharing the same Apache processes. It won't happen, for all the right reasons.
-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.