I am developing an applet and testing it in Netscape Navigator.I find that after I recompile, I press reload, clear the caches, retype the URL of the HTML wrapper, and I still have the old version. Why is this?
• A. It is because Netscape has completely failed to improve the defective code that does this monstrously wrong thing. It has been like this for many successive releases. Flushing the network cache will make no difference; that isn’t where the caching is taking place. Although applets are sometimes “pruned” and their ClassLoaders garbage-collected, this doesn’t happen predictably, so restarting Netscape is the only reliable work-around at the moment. A related question is “how do I make the browser reload from a URLConnection instead of just getting the content from the local cache?” The answer is to use java.net.URLConnection.setUseCaches(false) Browsers seem to vary in their conformance to this programmatic request. Netscape caching varies depending on whether a proxy server is in use, and which thread in the applet made the get request.
Related Questions
- I am developing an applet and testing it in Netscape Navigator.I find that after I recompile, I press reload, clear the caches, retype the URL of the HTML wrapper, and I still have the old version. Why is this?
- How do I make an applet reload in the netscape browser without quitting and restarting?
- What are the keyboard keys I press in Netscape/CosmoPlayer to move around the world?
