> -----Ursprüngliche Nachricht----- > von Garrett Rooney
> > Sticking per-backend info like ajp_flush_wait into the worker > object and the code to configure it in mod_proxy.c itself > seems very wrong to me. There should be a per-backend > contect pointer to hold per-backend information, and the work > of handling worker parameters really should be pushed to a > per-backend callback or something like that. I agree in general, but I guess in this case things are different. Although Jim chose names with ajp_ contained I think we can also use this to teach mod_proxy_http flushing. Not quite sure when I have time for this, but I want to give this a serious check as people also complainted frequently of this problem for mod_proxy_http. Regards Rüdiger
