-----Message d'origine----- >De : Nick Kew [mailto:[EMAIL PROTECTED] >Envoyé : lundi 17 septembre 2007 12:59 >À : dev@httpd.apache.org >Objet : Re: [PATCH] Apache 2.2.x: Implicit creation of new proxy_workers > >On Mon, 17 Sep 2007 11:33:16 +0200 >Axel-Stéphane SMORGRAV <[EMAIL PROTECTED]> wrote: > >Instead of limiting the number and thus creating them randomly (according >to what traffic happens to hit the server first), wouldn't it be better >to introduce a configuration directive to create your choice of those extra >workers at startup?
That configuration directive already exists: it's called ProxyPass. RewriteRule / http://server/ [P] ProxyPass / ! ProxyPass / http://server/ Been there, done that. Works well provided you have an exhaustive list of backends at the time the server is started. The list of our backends resides in a RewriteMap so that approach is not practical. >If your config is such that specifying the workers isn't going to work, then >managing them dynamically in a useful manner is going to be a complex job >that should probably have its own separate module, based on a reslist and a >usage-counting strategy to drop little-used workers. >Or something like that. A separate pool of dynamically created workers, of limited size known at configuration time, with a LRU replacement strategy whenever we run out of workers would indeed be a very elegant solution. I do not really see why this should be done in another module, though. BR -ascs
