Remy Maucherat wrote
After testing and benching, implementing buffering at the lower layer is
much better, as it avoids introducing complexity in all the levels of
processing, and is more powerful. The performance impact of the new
behavior is minimal (using a worst case scenario of a static
Steve Appling wrote:
Remy Maucherat wrote
After testing and benching, implementing buffering at the lower layer is
much better, as it avoids introducing complexity in all the levels of
processing, and is more powerful. The performance impact of the new
behavior is minimal (using a worst case
Steve Appling wrote:
The following patch combines the 3 packets that were generated for each
chunk into just one packet. There are more optimizations elsewhere - I'll
keep looking.
Patch of org.apache.coyote.http11.filters.ChunkedOutputFilter from 4.1.27
src.
After testing and benching,
On Fri, 12 Sep 2003, Remy Maucherat wrote:
Steve Appling wrote:
The following patch combines the 3 packets that were generated for each
chunk into just one packet. There are more optimizations elsewhere - I'll
keep looking.
Patch of
Steve Appling wrote:
The following patch combines the 3 packets that were generated for each
chunk into just one packet. There are more optimizations elsewhere - I'll
keep looking.
Patch of org.apache.coyote.http11.filters.ChunkedOutputFilter from 4.1.27
src.
The patch is bad right now, because
maybe I'm missing something, but http1.0 doesn't
support chunking. isn't it feasible to just make
tomcat respond with http1.0 instead for this
particular problem?
I'm probably being naive here, but you could use the
older connector instead.
peter
--- Remy Maucherat [EMAIL PROTECTED] wrote:
