Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Message-ID: <00b301bfccae$f0652700$0100007f@localhost>
From: "jlwpc1" <jlwpc1@earthlink.net>
To: <new-httpd@apache.org>
References: <000401bfcb6c$f49f72a0$345985d0@corecomm.net>
Subject: Re: Windows 2.0  MPM design issues
Date: Fri, 2 Jun 2000 08:12:55 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

From: William A. Rowe, Jr. <wrowe@lnd.com>

> > From: jlwpc1 [mailto:jlwpc1@earthlink.net]
> > Sent: Wednesday, May 31, 2000 5:47 PM
> >=20
> > Windows starts process A (Windows or Console) and main thread=20
> > Aa (process A thread a) and then what happens?
> >
> > Just in words what it is?
>=20
> In the new scheme?  We start in http_main() and start calling
> the MPM's hooks, in the order I just documented for you.
>=20
> Under Winnt's MPM, we are dual process;
>=20

Yes but there is no written down reason _why_ Apache is dual process in =
the Windows version. Why?

Windows is a multi-threaded OS not process - it looks like what Apache =
is doing would be cleaner and quicker using just threads.  So why is =
there another process used as if it were a thread?

Thanks,
JLW