Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Message-ID: <005b01bfa705$90ffedf0$c1e01b09@raleigh.ibm.com>
From: "Bill Stoddard" <stoddard@raleigh.ibm.com>
To: <new-httpd@apache.org>
References: <000101bfa703$93b55be0$345985d0@corecomm.net>
Subject: Re: [patches 2.0 & 1.3] src/os/win32/service
Date: Sat, 15 Apr 2000 14:08:13 -0400
Organization: IBM Corp.
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


> > From: Bill Stoddard [mailto:stoddard@raleigh.ibm.com]
> > Sent: Saturday, April 15, 2000 12:37 PM
> >
> > > 3) [both] Due to frequent complains of launching Apache as
> > a service,
> > >    and the difficulty of shooting down the issue (when Apache is
> > >    willing to launch from the command line), the patch to each
> > >    module will assure NT first launches TCPIP and AFP (winsock)
> > >    in order to assure that Apache launches smoothly at startup.
> > >
> > Cool. I was wondering how to do this.
> >
> > Bill
>
> So was I for the past month and a half.  I knew 'how' to do it,
> but didn't really know what we really depended on.  I didn't feel
> like breaking ServicePacked NT to find out :-)

I knew about AFP and of course TCP/IP.  A few of us here at IBM have written an in-kernel
HTTP engine for NT. We needed to punt cache misses to Apache, which ultimately required us
to completely bypassed AFP in favor of our own home grown light weight socket layer (for
performance reasons). Wish we'd done the work on Linux instead...

Bill