This really isn't a bug in Metadot, so much as it is a bug in Netscape (prior to verson 6), but it greatly
affects Metadot in certain situations.
The problem is that the table rendering mechanism in Netscape, prior to version 6, is extremely slow
when rendering nested tables as in the 'My Page' of Metadot. A page that may render instantly in MSIE,
or other browsers, can sometimes take 30 seconds or more to appear in Netscape. If you telnet directly
to the port, and type in the HTTP request, you can see that the page is delivered to the browser in a split
second, but with Netscape, you can also see that the CPU is pegged at 100% while it renders the page.
The obvious solution would be "upgrade to Netscape 6.0, or use another browser", but, unfortunately, this
is not an option. This is on a closed intranet with where many of the users (several thousand) have Sun
desktops with nothing but the "official corporate browser" (Netscape 4.5 or 4.7) available. As a
workaround, we have created a tool in the "My Page Toolbox", which directs the user to user another
browser if they can.
I haven't upgraded to 4.0 yet, so I apolgize if this has already been addressed. BTW, this is a great
product. I've used it several times on Solaris and various Linuxes including my home site.
Joe