Well don't you think that a single servlet or JSP handling all the request will
be an overhead
in term of performance as only one instance of the servlet handles all the
request in succession.
Thanks
Rajesh
Lance Lavandowska wrote:
> > I found your article really very useful, the idea of including rather
> > than redirecting seems an excellent proposition.
>
> Thank you.
>
> >
> > Now I've tried using a single servlet model wherein I have one servlet
> > included in all the presentaion JSP's, this servlet actually gets to
> > know which bean it has to coordinate for a specific page for
> > implementing the business logic and returns the results in a generic
> > fashion to the page, is this similar to what you have in mind when you
> > say a single servlet model .... or is it different...
>
> Yes, this is the same thing. Jakarta has released the Struts project, which
> provides a prewritten framework to handle all the "gruntwork" for you.
>
> >
> > Can you give me some leads, I would be most interested in knowing more
> > about it, you could additionally suggest pointers to more material like
> > this one.
>
> Besides www.javasoft.com/products/jsp/ one of the best sites to find
> information is javaworld.com. If you subscribe to the jsp-interest mailing
> list, the mail footers contain links to other useful sites & faqs.
>
> Lance
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
