> Can somebody highlight the advantages of using a applet VS Servlet for
> generating reports from a database.
The biggest "advantage" is if you need to be able to manipulate the data
at the browser. An applet could be written to get the whole data set and
do any sorting, filtering or graphing on the browser side. This would be
a faster (except for the initial request), more graphical UI and would
reduce resources needed at the server. A pure servlet solution will
require all processing to be done at the server, and generating graphics
if more complicated. Further, an HTML user interface is limited.
I think the general requirements/goals for the user interface should be
well defined before deciding which type of interface to use. If there is
only one simple report to display, or if there a browser restrictions
(must be supported by *any* browser), HTML is the way to go. If the
requirement is for a very robust, graphically oriented application that
includes complex sorting, filtering operations, a applet might be the
way to go.
Of course, the best solution is a design that will support both, and
will have high code reuse.
- Paul Philion
___________________________________________________________________________
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
