>> The problem is that the client asks for a page, then has to receive
>> it before it can be parsed and subsequent requests pipelined.
Perhaps I wasn't clear.
The client doesn't have to *completely* receive an HTML page to pipeline
subsequent requests. It is certainly feasible to build a browser which
parses the HTML as it is being read from TCP, and posts the subsequent
requests for inline graphics to the host at the earliest possible
moment. I.e. go ahead and post the GET's for the icons before you've
even hit the </HTML> tag of the initial GET. It might require a
multi-threaded design, but it could be done.
Depending on how large the initial page is versus the round trip time,
this could in many cases keep the window from slamming completely shut.
It would be interesting to prototype such a design and see how much of
an effect it would have.
--Tim Farley
XcelleNet, Inc.
This archive was generated by hypermail 2b29 : Mon Feb 14 2000 - 16:14:29 EST