Klaus Johannes Rusch
This is related to the issue raised by Jon below.
The browser seems to delay returning control in a linear
fashion based on the number of rows in the table. However,
if we step through the servlet server source code as the
HTTP response is built, we notice that the response is complete
and has already been sent back to the browser, but as soon
as an HTTP close connection is invoked in the servlet server,
the browser hangs for a long period of time.
There are several possiblities.
Is there any possible connection between the connection being
closed on the browser side and the web server
repeat triggering some kind of a frenzied processing in IE?
Does IE need to do some kind of indexing of a large document after
receiving it the first time? Would this be part of it's
"improved performance" optimizations?
Strangely, this doesn't happen if you read the table directly
from a web server normally or
Any insights would be greatly appreciated.
Substitute NoSpam.net with attglobal
4. signing in