This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
I was wondering if one of you experts could give me your opinion on the following approaches.  web start  applets  plugins We have a browser based reporting application. We would like to make this more interactive. A large number of classes would need to be passed to the client. Although we can take a download hit the very first time, successive requests must be fast to setup.  web start always checks for latest files on the server.  applets - can the classes be cached on the client?  plugins - would mean we actually install our classes into the browser plugin area. but would this mean multiple implementations to adapt our framework for each browser? thanks for any input... :roll: [ November 15, 2002: Message edited by: Neil Laurance ]
I can tell you a bit on . As you have a web application, at the moment, using JavaWebStart would mean: 1. write a new user interface based on Swing. (JavaWebStart is only a deployment facility for Swing applications, as I understand and use it. Please correct me, if this is wrong!) 2. JavaWebStart only checks for new updates if there is an internet connection and it downloads only new updates if there are any. Otherwise it starts the cached version (if you allow it to work offline). Starting the app offline is similar to starting it directly from an executable jar, e.g. Ok, JavaWebStart has to start up before the app, but I think the startup of the jvm itself is the most time consuming action and that one is indispensable. hope that cleared things up a bit Chantal