Why is Netscape slow in IIS 5.0?
A minor change introduced with IIS 5.0 may, in obscure situations, cause Netscape to render a page a bit slowly (though never by a minute, which I believe was an exaggeration by one individual). However, Microsoft did not to do this to thwart Netscape. All they did was change the response.buffer default property to “TRUE” (it was “FALSE” in IIS 4.0). When response.buffer is set to TRUE, the entire page is processed and stored in a “buffer” — not being sent to the client until the entire page is processed. When response.buffer is set to FALSE, the page is “streamed” to the client as it is processed – so you will some lines of text, then the server will churn out some more lines and they will appear, and so on until the page is finished.
