I agree on points where it is the UI "preetiness" that drives the decision to
use applets but there are reasons beyond UI that cause people to use
applet-servlet architecture.
In my current project for example I need to provide real time trading data to
the applet. This is done using custom protocol and delivered via HTTP tunneling
to allow users from behind firewalls to access the product. The UI is in AWT so
no plug-in is necessary.
How could this be achieved without an applet?
d.
Shital Kanitkar wrote:
> Hi,
>
> 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?
>
> Thanks,
> -Shital
>
> ___________________________________________________________________________
> 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
--
David Mossakowski [EMAIL PROTECTED]
Programmer 212.310.7275
Instinet Corporation
"I don't sit idly by, I'm planning a big surprise"
___________________________________________________________________________
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
