There are several good reasons not to use mod_perl, most of which become even better reasons in a shared environment:

• it's a memory hog;
• it's very easy to "corrupt" other processes and scripts running under it;
• it gives access to web server internals;
• buggy perl code can take down a lot more than just the one buggy CGI;
• and so on.

Now, some of those can be worked around, but not all of them, and to do so does not provide, for the vast majority of "use cases", sufficient benefit to justify doing the work in the first place. If you really want mod_perl, then hire a cheap machine. From the nice people who host the machine I run CPANdeps on, for example.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.