posted 23 years ago
Netscape 4.n has a notoriously bad display engine. Chances are that your response contains HTML that is taking the Netscape engine a long time to display. For example, deeply nested tables can drive it nuts! There are also certain combinations of CSS elements that I've found cause it to take forever to display the page.
If performance on Netscape 4.n is important for your app, you're best bet is to examine the resulting HTML for complexities (the deeply nested table instance being a likely suspect), and to simplify it when sending a respone to Netscape.
hth,
bear