If you run the 2-apache model described in the guide (as you generally
need on a busy site), you can use the locations set in ProxyPass
directives to determine which requests are passed to the backend
mod_perl apache and let the lightweight front end handle the
others directly. Or you can use mod_rewrite to almost arbitrarily
select which requests are run immediately by the front end or
proxied through to the back end server. You don't have to make
it visible to the outside by running the back end on a different
address - it can be another port accessed only by the front end
proxy.
Les Mikesell
[EMAIL PROTECTED]
----- Original Message -----
From: "Peiper,Richard" <[EMAIL PROTECTED]>
To: "'Jonathan Tweed'" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Wednesday, November 22, 2000 8:20 AM
Subject: RE: Question
>
> How could they not? Since the files are executable by any process,
> then all processes must have the mod_perl code in it. You could if you
> really wanted to run 2 versions of Apache, one with mod_perl and one
> without. You could then call all CGI's through a different IP and then run
> mod_perl on that one only. This would reduce the sizes of your executables
> running in memory for Apache.
>
> Richard
> Web Engineer
> ProAct Technologies Corp.
>
>
> > -----Original Message-----
> > From: Jonathan Tweed [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, November 22, 2000 9:15 AM
> > To: '[EMAIL PROTECTED]'
> > Subject: Question
> >
> >
> > Hi
> >
> > I would be grateful if someone could answer this question:
> >
> > Even if you tell Apache only to execute files in a certain
> > directory under
> > mod_perl do all processes still include the mod_perl code?
> >
> > Thanks
> >
> > Jonathan Tweed
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
