On Mon, 18 Jun 2001, Trevor Phillips wrote:
> Is there any way to control which daemon handles a certain request with apache
> 1.x?
http://perl.apache.org/guide/strategy.html#Running_More_than_One_mod_perl_S
> eg; Out of a pool of 50 daemons, restricting accesses to a certain mod_perl
> application to 10 specific daemons would improve the efficiency of data cached
> in those processes.
>
> If this is impossible in Apache 1.x, will it be possible in 2.x? I can really
> see a more advanced model for allocation improving efficiency and performance.
> Even if it isn't a hard-limit, but a preferential arrangement where, for
> example, hits to a particular URL tend to go to the same daemon(s), this would
> improve the efficiency of data cached within the daemon.
>
> I suppose I could do this now by having a front-end proxy, and mini-Apache
> configs for each "group" I want, but that seems to be going too far (at this
> stage), especially if the functionality already exists to do this within the
> one server.
>
> --
> . Trevor Phillips - http://jurai.murdoch.edu.au/ .
> : CWIS Systems Administrator - [EMAIL PROTECTED] :
> | IT Services - Murdoch University |
> >------------------- Member of the #SAS# & #CFC# --------------------<
> | On nights such as this, evil deeds are done. And good deeds, of /
> | course. But mostly evil, on the whole. /
> \ -- (Terry Pratchett, Wyrd Sisters) /
>
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
