Milt Epstein wrote:
> One thing servlet engines do to get
> around this is to create a pool of servlet instances, and if one
> instance is busy with a thread, one of the other instances will be
> used. This eliminates/reduces the performance penalty.
I believe this is only done in the case where the servlet implements interface
SingleThreadModel. Also I think synchronizing shared resources is the simplest
way to deal with multiple threads.
Gabriel Wong
http://www.ezwebtools.com
----------------------------
___________________________________________________________________________
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
