Would it make sense to use Worker for the front end, and prefork for the back end (assuming you want/need prefork for the backend) in this scenario?
Also, now that mod_deflate is part of the package, would it make sense to recommend running that as well. I ask all this because i set up a box for me to mess around with earlier this week like that. worker, with proxy and deflate on the frontend and prefork modperl on localhost. Adam -----Original Message----- From: Stas Bekman [mailto:[EMAIL PROTECTED] Sent: Fri 2/18/2005 9:12 PM To: Barry Hoggard Cc: mod_perl Subject: Re: setting up static and dynamic Apache 2.0 instructions for MP2 newbie Barry Hoggard wrote: > I am pretty comfortable with setting up a static front end that proxies > to a mod_perl server listening on 127.0.0.1 with Apache 1.x and mod_perl > 1.x, and mod_rpaf. > > Are there any caveats I should know about before getting this working on > 2.0 before I start setting it up? I have a stand-alone mod_perl/mod_ssl > server working now. Not that we know of, Barry. But if you encounter any problems, don't hesitate to report those here following these guidelines: http://perl.apache.org/bugs/ -- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
