comment on

2. mod_cgi - It has served us for years but it's getting quite old and what most people care for - it's slow.

Well so am I ... but seriously, I think the slow argument is not as valid as it once was. Copy-on-write has made fork on modern *nixes very efficient. So before you start calling mod_cgi slow, take a look at your *own* code and ensure it's not slow.

mod_cgi has a lot going for it *because* it's old - it's well understood, it's universal, it's cleaner, any script/executable can be run under it (I wouldn't be suprised to see java progs under mod_cgi as the JVM start-up times continue to improve).

-derby

In reply to Re: More than mod_cgi less than mod_perl. by derby
in thread More than mod_cgi less than mod_perl. by techcode

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks