> > I can't imagine how a web server cannot be affected by apps creating
> > threads and/or proccesses. Think about memmory use, resource
> > pooling, syncronization issues, ... remember a child process ot
> > thread prevents the termination of its parent (which may become a
> > zombie on Unix systems, and a zombie still holds its open file
> > handles).
>
> This is wrong. Parents *can* terminate with running children, and
> zombie processes take up no resources other than a process table slot.
In addition I don't think that if thread A spawns thread B that thread A has
to wait until thread B terminates before it can itself terminate. Why would
this be the case? Threads to not necessarily have the same parent child
relationships that processes do.
