Hi all, I plan to commit four more changes during the weekend. 2 of them are already coded and running, the other 2 ones I still need to implement. Most of the commits I did this week were only preparations for these functionally bigger ones.
Already done but not committed: - Passing back child worker names, lb_values and states from lb to apache via notes entries, such that you can easily log the names and states of the target workers via LogFormats (standard mod_log_config feature). This is very interesting to track your load balancer behaviour and much more poerful than the standard mod_jk request log (only for apache, I don't now a component similar to a notes table for the other web servers). - Rearranging runtime state and configuration state in the load balancer. At the moent there are a couple of status bits, which are actually not independent of each other. This poses some confusion in the configuration as well as in the status display. The change will be functionally compatible to the existing code, but there will be the new notions of runtime state (error, recovering, busy, ok, n/a) and configured activation (active, disabled, stop). To be coded during the weekend (subject to analysis of the related amount of work and risk): - hierarchical config for the balanced workers, s.t. you don't have to repeat the same attributes for all child workers of an lb. Individual child attributes will have preference. - The proposed enhancement of the pool model, to allow more connections then in the pool. Will need to think a little more about it's usefulness. And of course: add the new features to the docs. I would then make a snapshot available on dev, such that interested parties can compile and check, and could start a formal release process a week later. I know, that new features impose new risk, on the other hand the release process does also consume some energy, so personally I would prefer to not split these items into 2 or more releases. Comments? Regards, Rainer Yoav Shapira schrieb: > +1. > > And general kudos regarding the recent energy around the connectors. > > Yoav > > On 8/25/06, Mark Thomas <[EMAIL PROTECTED]> wrote: >> Mladen Turk wrote: >> > Hi, >> > >> > There is one serious bug in 1.2.18 that makes >> > it unusable for IIS if there is a missing optional >> > directive (rewrite_rule_file). >> >> Thanks for your message on the users list about this. >> >> > Since we had already lots of commits fixing various >> > problems, 1.2.19 is something we should cut pretty >> > soon. >> > Any comments or pending work? >> > I would like that we make this release next week. >> >> Sounds like a good idea to me. >> >> Mark >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
