Re: Gnat.Sockets and non-blocking connects

[Jano <nono@celes.unizar.es>]

Florian Weimer dice...
> Samuel Tardieu <sam@rfc1149.net> writes:
> 
> >>>>>> "Florian" == Florian Weimer <fw@deneb.enyo.de> writes:
> >
> > Florian> Errors are reported by the R/W selectors.  However,
> > Florian> nonblocking connect error reporting is not portable, see
> > Florian> Steven's UNIX Network Programming.
> >
> > In practice, it *is* portable.
> 
> The SO_ERROR socket option is implemented in two different ways.
> 
> > Jano, you need to check the write set,
> 
> Correct.
> 
> > and try to connect again. You will get an error. If the error is
> > EISCONN, you *are* connected. If this is anything else, you
> > *aren't*.
> 
> Unfortunately, you don't get the error code in this case.

Mmm, I've found two workarounds for Windows:

* Trying to connect again will give an error while connecting, or will 
return again Operation_would_block (that means you have failed and are 
trying again, so it's kinda lame solution).

* Getting the remote address of the socket gives two different errors 
when connecting and failed.

Remember, I have no problem detecting the connection is successful. (My 
comments about the exception set were taken directly from the Windows 
help for Select).

However, I suppose that will not work in Linux. Oh well, really I hope 
these folks can get right a nice networking package for 0Y.

-- 
-------------------------
Jano
402450.at.cepsz.unizar.es
-------------------------