httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Reid" <dr...@jetnet.co.uk>
Subject Re: What is the purpose of saferead?
Date Wed, 14 Jun 2000 14:14:53 GMT
I found the solution!  BeOS hadn't added the timeout options, so once I did
that and added a case to deal with the saferead it was working again.

Wednesady, must be Glasgow...

david

----- Original Message -----
From: "Bill Stoddard" <stoddard@raleigh.ibm.com>
To: <new-httpd@apache.org>
Sent: Wednesday, June 14, 2000 3:15 PM
Subject: Re: What is the purpose of saferead?


>
> > 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
>
>


Mime
View raw message