I'm sorry to say it, but I think these guys are on the wrong track. To get the environment they're trying to build in mod_perl, all you have to do is set MaxRequestsPerChild to 1. Then the processes exit after one request and you get a fresh, pre-forked process with a pristine Perl interpreter for the next request. You can do something similar with FastCGI, and FastCGI already has the wide availability in cheap ISPs that they say they want. In fact, mod_perl even already has the feature they want with blessed modules that stay in memory: just load them in startup before forking and they will be there already compiled, even with the MaxRequestsPerChild approach.

Why does no one do this with mod_perl or FastCGI? Because the performance is pretty bad compared to letting your code, database handles, and cached data stick around between requests.

---

---

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.