If you are talking JSP vs applet, I think the applet gives the user a richer experience. That said, there are other issues you need to deal with when using applets, such as client JRE versions, browser/OS compatibility, etc. The other big difference is that JSP is served/rendered from the server, whereas the applet is run on the client, so you have different communication issues. IMHO, it depends on the application as to which approach is best. I just got done with a fantasy football project where we did a swing-based fantasy stat tracking applet with a tomcat/servlet backend. We used a polling model such that the applet would poll for its data every 30 seconds. This approach worked very well for that application - I would have felt constrained had I been limited to HTML or even DHTML. I would say as a general rule that the more dynamic the application, the more appropriate an applet might be - for more "static" applications that basically just render data, JSP might be more appropriate. My $.02 anyway.
Jeff ----- Original Message ----- From: "David Moran" <[EMAIL PROTECTED]> To: "Research Triangle Java User's Group mailing list." <[EMAIL PROTECTED]> Sent: Wednesday, September 29, 2004 9:28 AM Subject: [Juglist] Applets vs Servlets > I was recently evaluating a program that built its web interface using > applets that were converted from its java client application. The applets > are servered up from a tomcat server. I was wondering what the group > thought of this approach versus a more traditional J2EE approach and are > there any problems that this would cause that we should be aware of. > > > _______________________________________________ > Juglist mailing list > [EMAIL PROTECTED] > http://trijug.org/mailman/listinfo/juglist_trijug.org > > _______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
