Rajesh Nagarjunan wrote:
> 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.
>
Why would this create overhead? The servlets and JSP pages run in a multithreaded
environment already, and using only one instance (for a particular piece of
functionality) actually saves a little overhead -- by reducing memory occupancy --
versus having an object per simultaneous request.
The only place you will have synchronization issues between simultaneous requests
is when they are both trying to update the same object (and you are imposing some
sort of locking). But this will happen whether you have one or many instances of
the servlet or JSP page doing the changes.
>
> Thanks
> Rajesh
>
Craig McClanahan
===========================================================================
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
