> Well, you *always* have to make your servlet thread-safe.
>
> FWIW, my impression, mostly from past discussions on this list (you
> might look them up), is that SingleThreadModel is a bad idea, for
> performance reasons, and because it is not the panacea for thread
> safety that it at first appears, and hence can mislead you into
> thinking that your code is thread safe when it's not. The best thing
> is to design your code/system so that contention issues are avoided as
> much as possible, and when they might occur, synchronize the code on
> the smallest block possible. I realize that is easier said then done.
>
Let's call it what it is....SingleThreadModel is a hack for lazy engineers
who don't design their servlets properly and want to burden perfectly good
hardware. ;->
-phil
Phillip A. Lindsay
eBuilt, Inc. "Building the foundation for success"
___________________________________________________________________________
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
