Gary Almes wrote:
>
> I'm pretty sure that Netscape treats Javascript just like it does standard
> HTML, in that it does not cache the code. Every time a new page loads,
> Netscape must re-load the Javascript because Netscape has no way of knowing
> that the Javascript on the current page is identical to the Javascript on
> the previous page.
>
>
While that's true, Brent was asking about external javascript files.
These files would be kept in the browser's cache. As pointed out
elsewhere, this technique has a lot of similarity to Server Side
Includes.
One note of caution to anyone wanting to try external javascript files.
Make sure the server that will be dishing up the .js files is properly
configured to serve up the correct mime type. Version 4.X browsers
understand the .js file extension and know what to do with them, but
older browsers will display the raw html in the window if the server
isn't configured properly. I'd guess that anybody who is doing serious
work on the web would check their pages in a variety of browsers, but I
have noticed a number of web sites, especially those powered by some of
the proprietary web servers like the new FirstClass software, that are
broke when viewed with version 3.X browsers.
HTH
Rolf
____________________________________________________________________
--------------------------------------------------------------------
Join The Web Consultants Association : Register on our web site Now
Web Consultants Web Site : http://just4u.com/webconsultants
If you lose the instructions All subscription/unsubscribing can be done
directly from our website for all our lists.
---------------------------------------------------------------------
