My best shot at boiling all this into one sentence: Does the added complexity a two-Apache configuration offer performance improvements/overhead-reduction that make the complexity worthwhile?
It depends :-)
Did you read what the mod_perl guide has to say on this issue? If not, do it now: Choosing the Right Strategy is a very complete and helpful document.
Besides that, it really depends on your traffic. I never cared to set up a reverse-proxy (because my servers work fine without it), but if I ever get the feeling that the servers got slow, I'd implement it.
For some advanced setup issues, perrins articel Building a Large-Scale E-commerce site with Apache and mod_perl is a good read, too.
--
#!/usr/bin/perl
for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}
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.