Re: [OT] mod_proxy, mod_perl, php

[Perrin Harkins]

Scott Alexander wrote:

No mod_perl doesn't serve the documents. I'm just using a PerlTranshandler
to change the uri.

Okay, that should work then.

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.

I don't know; that's a PHP question.

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.

Sorry, I don't understand what you're talking about here.

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.

I don't see any good reason not to put PHP on the backend and do all the page generation there. It keeps the front-end simple too.

- Perrin