On Wed, 18 Dec 2002, Perrin Harkins wrote: > Scott Alexander wrote: > > At the moment I have a front_end server with no php support. > > > > Backend is mod_perl. I'm planning to extend our document management > > system to serve www pages. > > > > The html documents are on the mod_perl machine. What happens if users add > > php code to their html documents? > > Nothing, unless you add PHP support to that machine and make sure > mod_perl is not serving those documents. You can't have them both > handle the same documents. >
No mod_perl doesn't serve the documents. I'm just using a PerlTranshandler to change the uri. > > If I add php support on the front_end will it work normally? > > No, not if the front-end is proxying. It has to be actually serving > those documents locally in order to run them through PHP. > > - Perrin > So if I add php support to the mod_perl server. How much extra load/memory usage strain will it add to the mod_perl server. The setup is front_end 2*550 PIII scsi drives 2 GB mod_perl server 2*1200 scsi 36 GB 2GB database server 2*1200 scsi 36 GB 2GB About 30000 - 50000 scripts per day plus 5000 rewrites using the PerlTranshandler for the web pages. Database machine is handling abou 2 million queries per day. If I add a www -management system to our existing intranet application I want that all the www pages are in the www -management system not php pages on the front_end (have to add php support of course) and html pages on the mod_perl server. Or would it be better to have a nfs on the front_end accessible from the mod_perl server. So users can update the documents using the intranet application. Then www requests are handled only by the front end with now added php support. Best Regards Scott
