As you know, I have been concerned about the size of the JmolApplet. I recently did some more research and found some good news.
The size of the applet is a problem for end-users who may have slow connections. Previously, the applet was only cached in the web-browser cache, so it could be flushed from the cache for occasional users. Sun's Java Plug-in has a separate cache that it maintains outside of the browser. Previously, this cache was only used for applets that were identified by the OBJECT/EMBED tags, but not the APPLET tag. As of version 1.4.1, .jar files that are in the ARCHIVE tag of the APPLET tag now automatically get cached by the Java Plug-in. When an applet is run, the plug-in compares the date and size of the applet on the server. If it has changed, then the new applet is downloaded. I have done some testing and confirmed that it seems to function as designed (at least on my Linux system). I can delete my browser cache and see that the applet still launches quickly. This only affects users who are running the Java Plug-in: - Linux/unix - Mac OS X - Win32 Mozilla - Win32 IE (*if* the user installs the Sun Java Plug-in). It does not affect: - Win32 IE + Msft JVM - Win32 & Mac Netscape 4.* Note: that because of the legal disputes between MSFT and SUN, all IE users will need to start migrating to the Sun Java Plug-in over time) Note: This does *not* directly address any issues related to offline-use Miguel ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Jmol-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jmol-developers
