Noticed that IE was twice as fast when when rendering a Silverstream html page. Why? Is silverstream optimized for IE? Are there any tricks we can do to tailor our code to Netscape? Anyone have any related experience?
I think your Netscape being twice as fast is probably due to your IE5 having previously cached the silverstream pages.
Silverstream does seem however to have geared its HTML generation to Netscape. However I think this will change with 3.5 as that has dreamwweaver integration. Hopefully they will be able to address the integration probelms.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.