* Adam Tilghman [EMAIL PROTECTED] wrote:
snip
It seems to me that running in reverse proxy mode as you suggest would
require one running instance per possible UID, which would be fine for
tens or even hundreds of users, but not for the number we have to support.
You're probably interested in
On May 15, 2004, at 12:25 PM, Adam Tilghman wrote:
I'm writing a module which plays with seteuid/setegid,
and should therefore only be run under the prefork MPM.
at low level your reliance is on a single-threaded process handling
requests?
That's correct - I'm switching UID/GID on every request
That's correct - I'm switching UID/GID on every request based on
the provided authenticated username. It seems to me a multi-threaded
server wouldn't be able to handle this situation very well.
You know, I'd recommend using apache in reverse proxy mode.
[...]
Of course, this would assume you
I'm writing a module which plays with seteuid/setegid,
and should therefore only be run under the prefork MPM.
at low level your reliance is on a single-threaded process handling
requests?
That's correct - I'm switching UID/GID on every request based on
the provided authenticated username.
Adam Tilghman wrote:
Hi,
I'm writing a module which plays with seteuid/setegid,
and should therefore only be run under the prefork MPM.
at low level your reliance is on a single-threaded process handling requests?
ap_mpm_query() can check for such MPM characteristics
