Paul Holser wrote:
>
> as a follow-up question, has anyone done benchmarks highlighting
> the differences between a SingleThreadModel controller servlet and
> a non-SingleThreadModel controller servlet? if i understand
> SingleThreadModel correctly, it signals to the servlet engine that
> it can "pool" instances of the servlet, mitigating to a degree the
> constraint of one thread at a time through the servlet's service().
>
I haven't done any benchmarks, but I don't see any way an STM (SingleThreadModel)
servlet can really be *faster* than a non-STM servlet. Given that plus the fact
that STM only protects you from *part* of the complexity of multithread
programming, not all of it, I avoid STM like the plague.
Note that providing a pool of STM servlets is commonly supported, but it is not
required by the spec. It's entirely legal to have only one instance. Check the
docs for your server to make sure.
>
> thx,
> p
>
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
