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=true" 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.
That's not a valid arguement; most 'users' are either the authors of the
affected applications, or the users who are trusting the word of the author
is their release notes.
Go with mod_jk's solution. Disable the optimization by default and adopt
the slower behavior for robustness and reliability. And give application
authors the ability to optimize, or to report that the optimization is safe
in their release notes.
Bill
