Hello world...
I am quite new to servlets, I have been experimenting with them for two
months and a subscriber to the list for a month. In the books by Jason
Hunter and Karl Moss, in several discussions on the list and in various
tutorials around the net I have read about Servlet Chaining. I know how
it is done, I know what I can use it for but I do not know if there are
any real reasons for using it.
I have seen Servlet Chaining-examples where one servlet would receive
the user's request and do something with it (search in a database) and
another servlet would format the output (turn ResultSet into <table>).
In my project we have chosen a different approach; we have, for
instance, created a class that opens HTML-documents and adds dynamic
content from a database. This class is used by our servlets; the
servlets parse the request and decide what content is to be added to the
existing page in every individual case. The servlets create objects of
our utility-class and let these objects do the actual work (opening a
File, querying the database, parsing the HTML etc). My question is
whether there is any reason for us to use Servlet Chaining instead?
Would response times be shorter or longer?
Some of our utility things could be implemented using JSP. Should we?
Would that be faster, safer, more scalable, more reliable, etc?
What about security-issues?
What other reasons would there be for choosing a particular approach?
Thanks in advance,
/Micael Kallman
Micael K�llman [EMAIL PROTECTED] 018-167709
___________________________________________________________________________
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
