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.
For the benefit of folks here and not on mod_jk; IIUC somewhere midstream
the semi-stable releases of mod_jk (post 1.2.8), the flush logic had this
same 'optimization' added by default. In more recent and quite stable
mod_jk's (1.2.14'ish timeframe), this change was reversed out such that
it once again flushes by default, with the patch retained to allow them
to optimize it when appropriate?
Bill
