RE: Application vs. Applets vs. Servlets -- JAVA400-L

Rich,
You are correct in regard to item 2.  I was approaching the servlet/applet
question from a public network application rather then someone who has "multiple
use" users of the application.  Applets make sense in a Intranet environment
where the users are regular, when you face new users all the time then the
downloads become burdensome.
Royce


|--------+------------------------->
|        |          "Haney, Rich"  |
|        |          <rich_haney@gil|
|        |          barco.com>     |
|        |                         |
|        |          09/30/99 08:13 |
|        |          AM             |
|        |          Please respond |
|        |          to JAVA400-L   |
|        |                         |
|--------+------------------------->
  >----------------------------------------------------------------|
  |                                                                |
  |       To:     "'JAVA400-L@midrange.com'"                       |
  |       <JAVA400-L@midrange.com>                                 |
  |       cc:     (bcc: Royce Stearns/Manage)                      |
  |       Subject:     RE: Application vs. Applets vs. Servlets    |
  >----------------------------------------------------------------|





As a servlet and JSP enthusiast in general I agree with 1.) and 3.) in
general, but as to 2.) believe that applets are only downloaded to a client
if they are more recent than the version on the server ( or they do not
exist at all on the client ).  So, after the first time a given version of
an applet is used, there is no downloading that occurs. Correct me if I am
wrong.  If I am wrong, then Sun et. al. are also then considerably dumber
than Microsoft and its use of ActiveX technology, which would lead to me to
do heavy drinking to say the least.

Regarding 3.) I believe that a Swing applet right on the desktop is somewhat
faster than an applet getting HTML remotely, but that most users would not
notice the difference unless it is a very graphics-intensive situation.
That becomes the one situation I would use an applet.  So I would be apt to
use applets only for very complex user interfaces, or for very
graphics-intensive situations, namely about 10-15% of the time.  The the
rest of the time I use servlets or JSP's.  I would use applications
downloaded to the user's own machine ( the client ) 0% of the time, that is,
not at all. )


-----Original Message-----
From: rstearns@mpire.net [mailto:rstearns@mpire.net]
Sent: Wednesday, September 29, 1999 8:14 PM
To: JAVA400-L@midrange.com
Subject: RE: Application vs. Applets vs. Servlets


Actually the servlet can be quite a  bit faster then the applet for a couple
reasons. 1) Once started a servlet isn't stopped and started with each
request
and the servlet can actually be pre-started with the server.  2) No class
download is required to the client since everything is resident on the
server.
3) The only thing running on the client browser is HTML (pretty fast).
Royce


|--------+----------------------->
|        |          nimrod@jacada|
|        |          .com         |
|        |                       |
|        |          09/29/99     |
|        |          03:01 PM     |
|        |          Please       |
|        |          respond to   |
|        |          JAVA400-L    |
|        |                       |
|--------+----------------------->
  >----------------------------------------------------------------|
  |                                                                |
  |       To:     JAVA400-L@midrange.com                           |
  |       cc:     (bcc: Royce Stearns/Manage)                      |
  |       Subject:     RE: Application vs. Applets vs. Servlets    |
  >----------------------------------------------------------------|








> I agree with everything said the contributor Nimrod, and would say his
> points in about the same way.
>
> However, I don't know why applets should in general be slower than
> applications.
>
> Is this be a difference between the use of a true optimizing compiler for
> applications, but only a JIT compiler for applets?  ( Since applets
usually
> contain only user interface stuff, I am not sure why a compiler
difference
> would matter. )  Or, is there something else going on?
I guess the simple answer is that if you do all your business logic in
the applet (no back-end logic), then the applet has to access the data-
bases over the network.  This alone can cost you an arm and a leg in
terms of performance.  Other than that applets in the real world will
usually perform better than Java on the '400, because you have much
more CPU power on your desktop than the portion you get out of your
server.

Nimrod


+---
| 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
+---



+---
| 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
+---
+---
| 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
+---



+---
| 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
+---