> > > with servlet and jsp, it's so easy to build the web > > > page, why still need the applet? in what situation, > > > applet is more suitable? > > > > Some reasons (and there are a lot more): > > - ability to keep permanent connections > > - ability to have a full-blown GUI with all a desktop app can have (there > > are lots of things you cannot model with HTML and CSS) > > - ability to put logic on the client (keyword "thick client") > > - independence of the browser (In most cases a complex, dynamic client UI > > can be build simpler when using an applet than by using client-side > > scripting langs) > > Any document to support these points..? >
Uhm, no... But how do you keep a permanent connection to a server/servlet without using an applet ? All other points I listed could be done by scripts and HTML controls. But how do you implement a complex GUI in a browser-independ way? If you're using client-side scripting, you'll have a different script for almost every browser you want to support. And what if scripting is disabled? It's just much simpler to use an applet in such cases, it's not the only way. Maybe it's just because I don't like JavaScript or how browser vendors implement it in their products :-D -mw ___________________________________________________________________________ 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
