Lew <l...@nospam.lewscanon.com> wrote:

I am concerned with the additional difficulties of thread management when the
Web container itself is trying to manage threads.  Concurrent programming is
fraught with peril even when the programmer has a measure of control over the
whole process.  In a Web container with multiple applications existent
ignorant of each other, and its own thread policies, small mistakes can have
devastating consequences.

I'm sure it's possible and even occasionally useful to explicitly spawn
threads in a web container environment, but there is much more care needed not
to interfere with what the web container does.  A badly managed thread could
damage not only the application that spawned it but every application running
on the server.

Your example seems to imply a limited context where threads are born and die
within the handling of a single request.  There the risks are much more
contained, and an error-free implementation seems easier.  For such a thing I
can see a smart programmer making good use of the idiom, but it isn't
something to abuse or take lightly.

I would never make a blanket statement about never doing something.