On 04/14/2010 05:45 PM, Jim Jagielski wrote: > > On Apr 14, 2010, at 3:38 AM, jean-frederic clere wrote: > >> On 04/13/2010 10:35 PM, Jim Jagielski wrote: >>> >>> On Apr 13, 2010, at 4:29 PM, Jim Jagielski wrote: >>> >>>> >>>> On Apr 8, 2010, at 3:58 AM, jean-frederic clere wrote: >>>> >>>>> On 04/07/2010 03:40 PM, "Plüm, Rüdiger, VF-Group" wrote: >>>>>> >>>>>> >>>>>>> -----Original Message----- >>>>>>> From: jean-frederic clere [mailto:[email protected]] >>>>>>> Sent: Mittwoch, 7. April 2010 15:32 >>>>>>> To: [email protected] >>>>>>> Subject: Arranging mod_proxy_balancer in trunk >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> In mod_proxy_balancer after >>>>>>> runtime = find_session_route(*balancer, r, &route, &sticky, url); >>>>>>> >>>>>>> There is a logic that belongs to the LB implementation, my >>>>>>> idea is to add a >>>>>>> apr_status_t (*updatelbstatus)(proxy_balancer *balancer, proxy_worker >>>>>>> *elected, server_rec *s); >>>>>>> in the proxy_balancer_method (mod_proxy.h) and call the LB >>>>>>> implementation. >>>>>>> >>>>>>> Comments? >>>>>> >>> >>> You should also likely pass a int * (or something) to handle >>> the requirement to also "know" total_factor outside of that >>> call... Of course, lbstatus is something that outside code >>> shouldn't really know about, but that's a whole 'nother >>> point ;) >> >> total_factor in fact depends on the LB implementation I don't think it >> should go outside it. >> > > I agree... So elected == runtime then??
Well you meant we don't need runtime and could use *worker instead don't you? Cheers Jean-Frederic
