Craig R. McClanahan wrote:
>I don't know of anyone working on it at the moment, although (at least for
>Tomcat 4) it would be a fairly straightforward exercise.
>
I think I have seen support for this in the code (see
org.apache.catalina.core.StandardWrapper), but I've also heard that the
STM servlet support is not as robust as it could be. Anyone with more
direct (codewise) experience on this care to comment?
>Personally, I don't think STM should be encouraged -- it misleads people
>into thinking they don't have to deal with multiple thread issues, and
>still runs into scalability problems when you hit the maximum configured
>number of instances for each given servlet. But I'd commit a patch to
>enable this if someone really wanted it.
>
While I agree that people should think about threading issues from the
get-go, and ideally always use multithreaded servlets, there are always
cases where (somehow) large amounts of non-threadsafe servlet code gets
written. When the dev team finally figures out how they've gone wrong,
they usually don't want to rewrite the whole app, they just want it to work.
Of course if you are building a high-traffic webapp you will want to
make sure everything is multithreaded, but for many low-traffic apps,
single-threaded models (while arguably uglier from a design standpoint)
perform just fine.
- jonathan.
