Re: CYGWIN blocking reads?

----- Original Message -----
From: "Henrik Nordstrom" <hno@marasystems.com>
To: "Robert Collins" <robert.collins@itdomain.com.au>
Cc: <squid-dev@squid-cache.org>
Sent: Monday, July 16, 2001 11:10 PM
Subject: Re: CYGWIN blocking reads?

> Robert Collins wrote:
>
> > I haven't re-tested this. Cygwin does support non-blocking I/O - and we
are
> > using it. However for some reason a read on a non-ready socket was
> > blocking!.
>
> Which the same as saying Cygwin does not support non-blocking I/O, at
least
> not on read().

Well cygwin is _meant_ to support non blocking I/O.

> Note: Using select() is NOT the same as non-blocking I/O. non-blocking I/O
is
> returning EAGAIN when read/write/accept/whatever otherwise would have
blocked.
> select()/poll() is commonly used in conjunction with non-blocking I/O to
avoid
> having to spin around polling all your file handles, but there are
> non-blocking I/O uses where select()/poll() is not used (for example a
> CPU intensive task needing to accept console commands).

Yes. I realise that. Anyway, I'll need to write up a test case and then
delve into the cygwin 'kernel' to track this down. I'll report back here
when I have a solid answer as the to current state.
Rob

> --
> Henriik
>
>
>
Received on Mon Jul 16 2001 - 15:36:19 MDT