× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Application vs. Applets vs. Servlets
  • From: rstearns@xxxxxxxxx
  • Date: Wed, 29 Sep 1999 17:13:30 -0700

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.