Re: Problems with non-blocking I/O

On Wed, Mar 26, 2003 at 11:32:20AM +1100, Tim Allen wrote: > time when selected for write. If you pause (eg ctrl-S) the client, you can > see it even more clearly. The server should (and on linux does) itself pause > in that situation, waiting to be able to write to the socket. On cygwin it > in

Re: Problems with non-blocking I/O

> I guess cygwin doesn't get a lot of testing with non-blocking I/O. We're > having lots of problems. Using version 1.3.14, we find it barely usable but > problematic and unreliable. With versions 1.3.20 and 1.3.21, it's quite > unusable. The specific problems are, for 1.3.14: > > 1. selecting for

Problems with non-blocking I/O

I guess cygwin doesn't get a lot of testing with non-blocking I/O. We're having lots of problems. Using version 1.3.14, we find it barely usable but problematic and unreliable. With versions 1.3.20 and 1.3.21, it's quite unusable. The specific problems are, for 1.3.14: 1. selecting for writing