Shital Kanitkar wrote:
>
> There has been a lot of discussion on this forum on Applet-Servlet
> Communication. I too selected this architecture for my project. I personally
> chose Applets 'cause I wanted to use Swing. But I see some practical
> problems in using Swing on the Web. The throughput is terrible. So why would
> anyone want to go in for this kind of an architecture, other than for pure
> academic purposes?
You would use an applet (or application) if you need a user interface
that can't be handled by an html page. For example, on a project I
worked we needed to be able to show a map to the user, draw polygons on
the map based on data in a database, and allow the user to draw polygons
on the map and have that data be stored back to the database. You can't
do that with html, so we used a Swing applet.
If all the user interface needs to do is show information, and get user
picks from checkboxes, lists, etc., then html can usually do the job
just fine.
K Mukhar
___________________________________________________________________________
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
