Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (athena.apache.org: 76.96.62.16 is neither permitted nor
 denied by domain of jim@jagunet.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: mod_lbmethod_byrequests required to define a BalancerMember
From: Jim Jagielski <jim@jaguNET.com>
In-Reply-To: 
 <CALK=YjOWtPLuuwxX9VGCPvCbw=MCXmyOC189DAdSjiE0AL=uww@mail.gmail.com>
Date: Thu, 3 Jan 2013 15:39:56 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <96DDA07A-3818-45A7-8A29-0943B1C3193B@jaguNET.com>
References: 
 <CALK=YjOWtPLuuwxX9VGCPvCbw=MCXmyOC189DAdSjiE0AL=uww@mail.gmail.com>
To: dev@httpd.apache.org

We should be able to defer that until we actually
*need* to start, as we do with other settings in trunk.

I can work on that in trunk and the propose a backport
to 2.4...

On Dec 28, 2012, at 11:11 AM, Eric Covener <covener@gmail.com> wrote:

> When defining a balancer, mod_lbmethod_byrequests is always looked up
> explicitly and used as the initial LB method.
> 
> I am curious how others feel about this:
> 
> [ ] document that mod_lbmethod_byrequests needs to be loaded and
> improve the error
> [ ] make it work if ProxySet lbmethod=other occurs before BalancerMember
> [ ] make it work if  ProxySet lbmethod=other occurs after BalancerMember
> [ ] refactor byrequests back into mod_proxy or mod_proxy_balancer so
> it's always available
> 
> --
> Eric Covener
> covener@gmail.com
>