According to Tom Brown:
>
> strikes me (as an owner of a web hosting service) that DSO is the wrong
> answer. What does DSO buy you? NOTHING except a complete waste of
> memory...
It doesn't really hurt anything but you still want a proxy.
> it strikes me that you _want_ a frontend proxy to feed your requests to
> the smallest number of backend daemons which are most likely to already
> have compiled your scripts. This saves memory and CPU, while simplifying
> the configuration, and of course, for a dedicated backend daemon, DSO buys
> nothing... even if that daemon uses access handlers, it still always needs
> mod_perl
If someone is ambitious enough to write some C code, what you really
need is a way for mod_proxy to actually start a new backend if
none are already running for a particular vhost. Then the
backend processes should extend the concept of killing off
excess children to the point of completely exiting after a
certain length of inactivity. The same approach could also
work for running scripts under different userids. I think
sometime in the distant past I have seen programs started
by inetd that would continue to listen in standalone mode
for a while to make subsequent connections faster but I
don't recall how it worked.
Les Mikesell
[EMAIL PROTECTED]
