Contact: Tel: 2726 - New Media Systems, 1st Floor South, Queens Walk
Nic,
I have to say, and I am quite sure most people will agree, that you have gone a
little bit extreme. Although I am now a fun of JSP and servlets, when other
tools can not do the job better then the applet can, then there is no reason why
people should not use it. An obvious area of applications is the graphics (not
image) drawing on the web page. Imagine you have a live database that store live
data and you would like to visualise it on the web page at real time. Without
using an applet, you would have to generate the image (not graphics) on the
server side and then pump the image data to the client, very slow.
I remember on earlier days I was so fond of using Perl CGI scripts. When
servlets came alone, I was a bit hesitated and then almost completely switched
to servlets. At one time I was worried that my Perl skills would not be needed
anywhere anymore. Gradually, I realised that in many applications, especially a
quick text-parser based applications, Perl is still the best (personally opinion
of course). The point is, knowing to use the right tool to do the right job is
better then biased to one tool only.
Perhaps using swing in applets have caused most of the grief in applet
programming because of the portability. Simply avoid it if you can.
Cheers,
Charles
Nic Ferrier <[EMAIL PROTECTED]> on 10/10/2000 05:30:47 PM
To: [EMAIL PROTECTED]
cc: (bcc: Charles Chen/YellowPages)
From: Nic Ferrier <[EMAIL PROTECTED]>, 10 October 2000, 5:30
p.m.
Re: Practical Application of Applet-Servlet Communication [Scanned by Yellow
Pages PostMaster]
>>> Shital Kanitkar <[EMAIL PROTECTED]> 10-Oct-00 5:08:20 PM >>>
>But I see some practical problems in using Swing on the
>Web.
>The throughput is terrible.
- lots of browsers don't support it properly
- the Java plugin is a pain in the neck
- it's slow
- it's memory hungry
>So why would anyone want to go in for this kind of an
>architecture, other than for pure academic purposes?
IMHO mostly coz people are not thinking about how to avoid using
them.
A lot of people seem to have an inability to deal with the
restrictions placed by the web... if you work within those
restrictions life gets much easier. It seems that most people can't
move beyond the client-server paradigm.
The distributed web architecture *is* better. It's faster, more
flexible (accepting the obvious UI restraints) and easier to build.
People using Swing (and applets generally) are just making their
lives difficult.
Nic
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
