Re: svn commit: r1067178 - /httpd/httpd/trunk/modules/proxy/mod_proxy_balancer.c
On 04 Feb 2011, at 3:50 PM, j...@apache.org wrote: URL: http://svn.apache.org/viewvc?rev=1067178view=rev Log: And yet more balancer params that can be changed at runtime via the b-m application... next up, of course, is adding new workers ;) If it became possible to add workers on the fly in response to long running multicast DNS requests (zeroconf), it would be made of awesome. (ENOTIME right now) Regards, Graham --
Re: svn commit: r1067178 - /httpd/httpd/trunk/modules/proxy/mod_proxy_balancer.c
On Feb 4, 2011, at 10:29 AM, Graham Leggett wrote: On 04 Feb 2011, at 3:50 PM, j...@apache.org wrote: URL: http://svn.apache.org/viewvc?rev=1067178view=rev Log: And yet more balancer params that can be changed at runtime via the b-m application... next up, of course, is adding new workers ;) If it became possible to add workers on the fly in response to long running multicast DNS requests (zeroconf), it would be made of awesome. Right now, the idea is for Apache to respond to simple GET requests, ala balancer-manager, to add workers. Of course, anything authorized could send those GET requests ;) ;)
Re: svn commit: r1067178 - /httpd/httpd/trunk/modules/proxy/mod_proxy_balancer.c
On 04 Feb 2011, at 6:14 PM, Jim Jagielski wrote: Right now, the idea is for Apache to respond to simple GET requests, ala balancer-manager, to add workers. Of course, anything authorized could send those GET requests ;) ;) We've finished zeroconf-ing one inhouse application we use, and we're keen to do the same for httpd at some point as a possible balancer module. As long as there was some or other function we could call (optional or otherwise) when a worker was to be added or removed, that would be enough for us. Regards, Graham --
