Ryan Bloom <[EMAIL PROTECTED]> writes:
> Unless somebody objects, I will commit my latest patch to the threaded MPM later
>this weekend.
> This is the patch that implements a multi-process single acceptor/multi-worker model.
> This will allow us to finish fixing the threaded MPM.
How does this affect having more than one process trying to take over
the slots of a process which is going away?
What happens with graceful restart? Is there a limit on the number
of requests which will be served using the old configuration? (That
is something which I thought sucked with my
accept-thread/worker-thread MPM... I'm interested in how this problem
is approached.)
--
Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site:
http://www.geocities.com/SiliconValley/Park/9289/
Born in Roswell... married an alien...
- Single listener - multi-worker Ryan Bloom
- Re: Single listener - multi-worker Justin Erenkrantz
- Re: Single listener - multi-worker Ryan Bloom
- Re: Single listener - multi-worker William M. Perry
- Re: Single listener - multi-worker Greg Ames
- Re: Single listener - multi-worker Ryan Bloom
- Re: Single listener - multi-worker Justin Erenkrantz
- Re: Single listener - multi-worker Jeff Trawick
- Re: Single listener - multi-worker Ryan Bloom
- Re: Single listener - multi-worker Jeff Trawick
- Re: Single listener - multi-worker Ryan Bloom
- Re: Single listener - multi-worker Ryan Bloom
- Re: Single listener - multi-worker Greg Ames
- Re: Single listener - multi-worker Ryan Bloom
- Re: Single listener - multi-worker Greg Ames
- Re: Single listener - multi-worker Justin Erenkrantz
- Re: Single listener - multi-worker Ryan Bloom
- Re: Single listener - multi-worker Ryan Bloom
