This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am weighing using an ActiveX control vs. a JavaApplet for my web page. One factor is download time. If I install an ActiveX control on the client's PC, then it is there and won't need to be downloaded again. It looks to me like a Java Applet will be downloaded every time the user visits my web page. Is that correct? Will the browser cache the applet and only redownload it if it has changed?
The jar files that make up an applet will be cached by the browser. The user has the option of turning this off (in the Java Plugin control panel) but caching is on by default, and most users probably never venture into that control panel to change things.
The browser just checks if the date of the jar file has changed; if it hasn't, then it's not downloaded again.
Joined: Feb 04, 2009
Thanks for the answer. Since you did not mention it, I take it there is no way to install an applet on the client machine, so even if the user had browser caching turned off, the browser would find and use the installed applet.
Samuel Quiring wrote:Thanks for the answer. Since you did not mention it, I take it there is no way to install an applet on the client machine, so even if the user had browser caching turned off, the browser would find and use the installed applet.
You might want to look into "Java Web Start", which exists to solve the problems you describe.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Can Java Applets be stored on the client?