Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Message-ID: <007701bfd60f$47362ed0$c1e01b09@raleigh.ibm.com>
From: "Bill Stoddard" <stoddard@raleigh.ibm.com>
To: <new-httpd@apache.org>
References: <001501bfd602$7d7b3b50$c1e01b09@raleigh.ibm.com>
 <006601bfd60a$f82ae140$c1e01b09@raleigh.ibm.com>
Subject: Re: What is the purpose of saferead?
Date: Wed, 14 Jun 2000 10:46:09 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Yes, I have it now.  ioctlsocket should work, but since I am trying to avoid using select,
the logic will be a bit different from Unix.

Bill

> > It seems to be an optimization for handling pipelined requests. Rather than
immediately
> > flushing the output buffers after handling a request, we do a non-blocking read to see
> if
> > another request (presumably a pipelined request) is on the wire. If another request is
> > read, we handle it and the response can be pipelined back to the client along with the
> > earlier response. Is this about right?
> >
> > Doing the non-blocking read is really causing me a headache with Windows. I don't know
> how
> > to do a non-blocking read on Windows w/o using select (which is a performance hog). I
> can
> > do an async read, but managing the i/o buffer on an async read is more than I care to
> deal
> > with right now. Would it be acceptable to bypass the saferead on Windows and do an
> > unconditional flush on the output buffer when we are done handling the request?
> >
>
> Hummm, perhaps ioctlsocket will make a socket non-blocking.... Investigating...
>
> Bill
>