--- John Saylor <[EMAIL PROTECTED]> wrote: > 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.
is that it? from another response, there are other issues i need to be careful about. > 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. i think we will run multiple mod_perl apps in one or more servers. we are slowly adopting CGI::Application in current app and one of the advantage of it is that, when the time comes, i can just slam it to mod_perl and run without any or minor changes, or i hope. > 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:[EMAIL PROTECTED] > 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 ) > > thanks, James. ____________________________________________________________________________________ The fish are biting. Get more visitors on your site using Yahoo! Search Marketing. http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php