Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 80143 invoked from network); 15 Mar 2007 20:02:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Mar 2007 20:02:46 -0000 Received: (qmail 33913 invoked by uid 500); 15 Mar 2007 20:02:50 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 33388 invoked by uid 500); 15 Mar 2007 20:02:49 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 33371 invoked by uid 99); 15 Mar 2007 20:02:49 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Mar 2007 13:02:49 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [68.236.108.169] (HELO liex2.liaison-intl.com) (68.236.108.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Mar 2007 13:02:38 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: mod_perl implementation possibility Date: Thu, 15 Mar 2007 16:02:16 -0400 Message-ID: <788CE35B4DF22443A7AA542796706AB50118111B@liex2.liaison-intl.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: mod_perl implementation possibility Thread-Index: AcdnO9fGnHSlEUOvR+Gu9XZkV50rZAAACfSA From: "John Saylor" To: "James. L" , X-Virus-Checked: Checked by ClamAV on apache.org hi=20 i'd encourage you to look into mod_perl as it can be amazing in letting you get the most out of your hardware. as far as running multiple unrelated perl apps using mod_perl- i think it happens every day! you just need to program them accordingly. also, you can use virtual hosts under apache 1.3.x too. if you use appropriate naming for db handles, there should be no confusion. i'd also suggest you take a look at Apache::DBI. i don't know what framework you're using, or how you will segregate the apps. it might be better to have them all running under one webserver, or maybe you will need to start up a few of them. there are many mod_perl application frameworks that may help you get up and running more quickly. i know HTML::Mason and CGI::Application pretty well, and i think either could do what you want it to. with mod_perl you can do pretty much anything you want, it's just how much time do you have to spend programming to get it to work as you'd like. with the frameworks, there's even less programming that you need to do. good luck. -----Original Message----- From: James. L [mailto:perlwle@yahoo.com]=20 Sent: Thursday, March 15, 2007 3:55 PM having read modperl's doc and i am concerned about running multiple unrelated mod_perl apps on one server, such as 2 or 3 medium Perl apps. ( issue like database handler pollution etc which i know little about )