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 agree that the current default may be right for
some, but majorly bad for others :) :)
On Mar 7, 2006, at 2:58 PM, Mladen Turk wrote:
William A. Rowe, Jr. wrote:
support should be default (flushed) with the -option- to optimize
for those
apps who aren't harmed by streaming.
Right. We have two options, either to flush on each packet,
that BTW might or might not reflect the user 'out.flush();'
or keep like it is right now (flush if server response is
slow), with presumption that if the packet is slow, the flush
needs to be done.
The current implementation breaks a simple timeout write:
out.write("Hello");
Thread.sleep(2000);
out.write("World");
It will send the 'Hello', but only after additional thread
finishes and times out.
Regards,
Mladen.