There is a large possibility that a second application, based on the first one, will permanently be added to this server. This would be two apache servers running full time. If we need to have test versions of those running at the same time, all of a sudden we have four apache servers running at once. That is why I am concerned about the scalability of this.
As far as a third server, the reason I came to that conclusion was because of this same possibility. I see there is no necessity for that now, it just seemed more cleanly organized in my mind to have one server doing the port forwarding and the others handling requests associated with their particular application. Otherwise, you have one apache server both handling the port forwarding and doing the work for its application. Again, not bad, just a little more convoluted.
In reply to Re^2: mod_perl and module versions
by thedoe
in thread mod_perl and module versions
by thedoe
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |