Hi everybody,
I have a question regarding the architecture with servlets and JSPs:
I have seen many postings on these lists describing an architecture
with _one_ servlet that acts as the central handler and processes
_all_ requests. It chooses which action to be taken, executes that
action and forwards the request to the respective JSP for
displaying the results:
--> JSP
/
Requests --> Servlet ---> JSP
\
--> JSP
I wonder if there is not another option to design the program
flow for use cases that need several steps with user interaction:
You could "chain" servlets and JSPs with one separate servlet for
each step:
init.
request result request2 result
-------> servlet1 ------> JSP1 --------> servlet2 ------> JSP2 -> ...
Has anybody used this second approach for modelling use cases?
What are the advantages/disadvantages of either architecture?
Without having much expirience, I could imagine that the first
variant might have difficulties to scale up - as this single servlet
could turn out to be a bottleneck? On the other hand, it could be
easier to maintain the first version and todo the security handling.
What are the consequences for reuseability, flexibility,
internationalisation?
All comments are appriciated,
ingo.
___________________________________________________________________________
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
