*) These measurements were performed using Netscape Communicator 4.0 beta
1 with max 4 (default) simultaneous connections and HTTP/1.0 Keep-Alive
headers. The Netscape HTTP client implementation uses the HTTP/1.0 Keep-Alive
mechanism to allow for multiple HTTP messages to be transmitted on the
same TCP connection. It therefore used 8 connections compared to 42 for
the libwww HTTP/1.0 implementation, in which this feature was disabled.
**) These measurements were performed using Microsoft Internet Explorer
3.01 with max 6 (default) simultaneous connections and HTTP/1.0 Keep-Alive
headers. As Netscape Communicator, it uses the HTTP/1.0 Keep-Alive mechanism
to allow for multiple HTTP messages to be transmitted on the same TCP connection.
The total number of connections used in the test case is 6. We could not
make MSIE do cache validation.
