Good point.
You can make use of client-side processing/caching much more easily than an
html client.
Html fits simplier interfaces easily but if the user requires a higher level
of interaction, trying to attain this in html can sometimes be
counter-productive.
Jon
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 17, 1999 8:04 AM
To: [EMAIL PROTECTED]
Subject: Re: J2SE and J2EE spin from Sun
Ron Yust asks:
>>I'm confused. After reading Sun's J2EE Application Programming Model and
>>listening to EJB experts on these newsgroups, I was under the impression
>>that Java on the client was NOT the preferred method to deliver client
GUI.
>>But now on Sun's Java web page I find the following:
.
>Java technology running on the client, or desktop, has made dramatic
>improvements since the birth of the Java platform and is playing a key role
>in enterprises today, particularly in intranet and business-to-business
>applications.
>The biggest growth areas for Java technology on the client today are in
>business communications over intranets and the Internet. Major corporations
>are having great success developing and using client-based applets, which
>provide new services and functionality more quickly by avoiding the long
>development cycle of traditional programming languages.
[snip]
There are many types of GUI clients out there. A Java application as a
client
allows you to have a much richer set of widgets and a greater amount of
functionality. For example, asynchronous notification through JMS is easier
to
accomplish through Java than through an HTML client. Sure, you could use
polling
but have you considered the impact that it will have upon your network? How
about
a realtime graph of network performance? An applet only needs to receive
the data
updates portion but if you push a new GIF each time what impact will that do
on
your network?
francis
--
The best thing about standards is that
there are so many to choose from.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
