Justin Erenkrantz wrote: > > On 3/7/06, Jim Jagielski <[EMAIL PROTECTED]> wrote: > > I would suggest that the "bandaid" code no longer be > > compile time but rather runtime, using a > > "force-flush=3Dtrue" param to the AJP worker. > > I'd prefer that we not defer this decision to the users - we should > either enable it or don't. But, most admins won't have enough > knowledge to know when to force flushing or not. > > > I agree that the current default may be right for > > some, but majorly bad for others :) :) > > Without FLUSHING_BANDAID, httpd will queue up the data when Tomcat > doesn't plan on writing any more. That's bad. > > Unless/until AJP has a protocol revision, I think the code should stay > and be enabled by default. The only 'right' fix is to correct the > buggy underlying protocol. -- justin >
Feh. No way. The argument would hold true if mod_jk did not provide just the sort of control that you say we shouldn't provide to users/admins, and control that *varies* from setup to setup. Yes, the protocol itself is "incomplete" but a the current, non-changable setup is not the correct way to address it. -- =========================================================================== Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "If you can dodge a wrench, you can dodge a ball."
