FWIW... On one EIS (Executive Information System) project, my compatriots and I found that applets gave us: (1) A richer, more app-ish UI (2) enough of a load-time delay (even for smallish applets) that our executive target audience was instantly annoyed beyond recovery.
Basically, we learned that when a CFO/CEO/et cetera clicks on a link they don't want to see no stinkin' "loading" banners, progress bars or big grey rectangles. ...and there's also the issue of browser VMs, security, etc. --Ken > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of David Moran > Sent: Wednesday, September 29, 2004 9:29 AM > To: Research Triangle Java User's Group mailing list. > 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
