Sat, 1 Jan 2000 09:43:09 -0800
At 14:57 -0500 99/12/30, Kragen Sitaker wrote:
>OK, let's look at a hypothetical example --- a process of an
>Apache-like web server. Each Apache child does the following:
>1. sits and waits for a connection to come in;
>2. when a connection comes in, one of the children awakes,
>3. reads data from the connection,
>4. creates a response and sends it back,
>5. closes the connection, and
>6. goes back to waiting.
I would have each child note (in shared RAM) when it entered a non prompt
activity and when it exited. Another process running every few seconds
would watch for stuck children. When a child was overdue, delete it and
create a new one from wherever chidren come from. Perhaps an apology to the
browser is also possible.
Norman Hardy <http://www.mediacity.com/~norm>