Java applet speed (was Re: [oclug] Monitoring memory usage)
Frank Stratton - VE3YY
fstratton at sympatico.ca
Tue Feb 22 10:43:24 EST 2005
Since this all a little new to me, I will go back to the books and have a
look at your suggestion. I think what you are saying is to start up the
Applet viewer outside of the browser. Is this correct?
What I am attempting to do, search a database, display the data to the user,
he/she manipulates the data using a java program and then sends the data
back to the database. I can't use forms because of the nature of the data
and the way the data is stored in the data base. It is composed of a master
record and any number of sub-records. The Java program must validate that
the information is well formed before it is sent back. For obvious reasons
I want to have a platform independent method. I think I can live with the
slow speed if there is no other way. The number of update in a day is low
so it is not critical. I will remember that this is not a good method for
large fast updates.
The alternative is a Java program that the user downloads and installs and
that may be the best alternative.
From: oclug-bounces at lists.oclug.on.ca
[mailto:oclug-bounces at lists.oclug.on.ca]On Behalf Of Rod Giffin
Sent: February 22, 2005 10:03 AM
To: General Membership Discussion List
Subject: Re: Java applet speed (was Re: [oclug] Monitoring memory usage)
On Tue, February 22, 2005 9:15, Adrian Irving-Beer said:
> On Mon, Feb 21, 2005 at 10:43:49PM -0500, Frank Stratton - VE3YY wrote:
>> Now as for Java, I've been learning Java and I have noticed that
>> some of my applets run a little slow. Not sure why, but figured that
>> it was an interface problem with Micro$oft Internet Exploder,
>> although it also was slow with Firefox. Maybe I don't have my Apache
>> web server configured correctly. Someone mentioned Tomcat, but I've
>> been avoiding that since I don't know if that will cure my problem.
>> Any thoughts?
> I can't comment on the speed issue, but AFAIK, I don't see how Tomcat
> on a server side is going to speed up Java on the client side, which
> is just a function of running on the client's machine, no?
You're right. Tomcat is server side architecture - basically an
application engine that uses http as it's communication protocol. It
won't serve applets any faster than Apache httpd, in fact that's not where
the problem lies in the first place.
Applets are, well frankly they were a "good idea at the time", best left
to exploring how to write programs in Java. The idea is to store an
applicaiton on a web server, and deliver it to the user when they want it.
The problem is, web browsers have to start the users JVM in order to get
applets to work, and this is a time consuming task. Also, the
architecture that applets rely on is way too layered. Running a program
inside of a program, inside of a web browser, inside of a window is
ususally just too much for the system to work efficiently.
Instead, try your applets in the applet viewer that came with your JVM, or
try your applets in the simple browser written into Java.
OCLUG general discussion list
OCLUG at lists.oclug.on.ca
More information about the OCLUG