Re: non-blocking connect fails with no pending acceptors

[Thomas Bushnell BSG]

"Neal H. Walfield" <neal@walfield.org> writes:

> If a program calls connect on a non-blocking socket with no pending
> acceptors (i.e. threads calling accept on the listening end of a
> socket), connect fails with EWOULDBLOCK.  It is unclear to me if this
> behavior is POSIX-conforming or not [1], however, (1) there are programs
> which do not expect this behavior; and (2) connect on other systems
> does not block before the number of connects without a accept exceeds
> the listen queue length (we treat the queue length as the maximum
> number of threads which can block doing a connect).

You think the behavior should be to allow the connect to succeed
immediately?  Ok, that's fine, but what then happens when you try to
move data... should it block, waiting for the connection to actually
be made?

Thomas