comment on

Which of these is the better approach with respect to FastCGI?

It really doesn't matter all that much, you can even have independent fcgi scripts that use modules!

Take perlmonks for example, index.pl does everything, but its really N-number of index.pl running on N-different machines -- its the same code, same module running from one script, for maximum maximum benefit from persistence (responsiveness)

The reason we use modules is they make code-reuse and testing individual functions easy

So which parts you choose to keep persistent depends on usage rates/patterns-- keep the most popular stuff persistent, keep response times low ...

In reply to Re: Question on design for FastCGI by Anonymous Monk
in thread Question on design for FastCGI by Anonymous Monk

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.


more useful options
	PerlMonks