Yeah, just use the mod_proxy model and then proxy to different mod_perl
backend servers based on the URL itself.
At 01:17 PM 6/18/2001 +0800, Trevor Phillips wrote:
>Is there any way to control which daemon handles a certain request with apache
>1.x?
>
>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) /
__________________________________________________
Gunther Birznieks ([EMAIL PROTECTED])
eXtropia - The Open Web Technology Company
http://www.eXtropia.com/
