Re: Problems with non-blocking I/O

2003-03-27 Thread Corinna Vinschen
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

2003-03-26 Thread Elfyn McBratney
> 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

Problems with non-blocking I/O

2003-03-26 Thread Tim Allen
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. select

Re: Non-blocking I/O

2002-11-19 Thread Corinna Vinschen
On Tue, Nov 19, 2002 at 12:52:44PM +0100, Paolo Bonzini wrote: > How do I set-up non-blocking I/O with SIGIO or > SIGURG notifications under Cygwin? FIOASYNC > Also, what kinds of file handlers will it work on? Does it > work on sockets and tty's at least? With sockets o

Non-blocking I/O

2002-11-19 Thread Paolo Bonzini
How do I set-up non-blocking I/O with SIGIO or SIGURG notifications under Cygwin? The various Unices I know of use either F_SETFL+F_SETOWN (BSD-ish), I_SETSIG (STREAMS-ish), FIOASYNC+SIOCSPGRP, or FIOASYNC (but does this send signals?). Does any of these work with Cygwin or do I need another one