Select with nonblocking connects
Fri Jul 5 05:48:00 GMT 2002
On Fri, Jul 05, 2002 at 11:27:22AM +0200, Thomas Pfaff wrote:
> There was a message in cygwin ml regarding nonblocking connects with
> select. Will this be fixed to a unix compliant version or should i answer
> him that he should use the exceptfds to get failed connects signaled ?
We should try to create a Unix compliant behaviour but it doesn't hurt
to tell him to use exceptfds until that's fixed. So, go ahead.
Do you have an idea how to implement that?
AFAICS, Linux also returns the fd in writefd if the connect hasn't been
called yet and as long as no listen() has been called on the socket.
So, probably we could add a flag `dont_use_in_select' to fhandler_socket.
As long as it's 0, the SOCKET isn't used in a call to the Winsock
select() but it's set in writefd automatically.
The flag is set to 1 if a listen or a connect succeeds. After that,
it's given to Winsock select() as usual.
What do you think?
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:firstname.lastname@example.org
Red Hat, Inc.
More information about the Cygwin-developers