Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown

quick summary

Ranch Hand
Posts: 183
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I was wondering if one of you experts could give me your opinion on the following approaches.
[1] web start
[2] applets
[3] 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.
[1] web start always checks for latest files on the server.
[2] applets - can the classes be cached on the client?
[3] 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...
[ November 15, 2002: Message edited by: Neil Laurance ]
Ranch Hand
Posts: 508
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I can tell you a bit on [1].
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
Ranch Hand
Posts: 672
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Chantal is right.
Web Start is a good choice for you situation.
For my next trick, I'll need the help of a tiny ad ...
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic