RE: Application vs. Applets vs. Servlets

>However, I don't know why applets should in general be slower than
>applications.
--------
I don't think it's so much that applets are slower at execution time, but that
they require the program code to be downloaded each time.  It is this behavior
that makes applets so unattractive as a business solution.  They're only
practical for small, limited function programs - at which point it makes more
sense to switch entirely to HTML using servlets (and JSP!).

On the other hand, if complex logic and sophisticated graphical features are
required, it makes much more sense to use an application, since the application
is already resident on the workstation.  The biggest issue there is that your
classes may get out of date - but that could always be handled with some simple
code to query the server for the current version of each package used and
download new ones as necessary.  This gives you the benefits of distribution of
the applet approach, yet only requires a download once for the new software.

Joe Pluta
Moderator
http://www.java400.net, where the AS/400 speaks Java with an RPG accent


+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---