• Mart Lubbers's avatar
    fix timeout by checking the socket for errors · f7616a16
    Mart Lubbers authored
    In the old situation when the connect didn't immediately return, the
    socket was placed in a select.
    An error was throws only when the socket was in the exceptset. However,
    sockets are only in the exceptset in very particular cases (see man
    select). Unable to connect is not one of those cases.
    
    Therefore to actually check if a connection was refused, the error
    status must be checked with getsockopt.
    f7616a16
Name
Last commit
Last update
..
Clean System Files Loading commit data...
Linux_C Loading commit data...
ObjectIO Loading commit data...
Windows_C Loading commit data...
TCPChannelClass.dcl Loading commit data...
TCPChannelClass.icl Loading commit data...
TCPChannels.dcl Loading commit data...
TCPChannels.icl Loading commit data...
TCPDef.dcl Loading commit data...
TCPDef.icl Loading commit data...
TCPEvent.dcl Loading commit data...
TCPEvent.icl Loading commit data...
TCPIP.dcl Loading commit data...
TCPIP.icl Loading commit data...
TCPStringChannels.dcl Loading commit data...
TCPStringChannels.icl Loading commit data...
TCPStringChannelsInternal.dcl Loading commit data...
TCPStringChannelsInternal.icl Loading commit data...
ostcp.dcl Loading commit data...
ostcp.icl Loading commit data...
tcp.dcl Loading commit data...
tcp.icl Loading commit data...
tcp_bytestreams.dcl Loading commit data...
tcp_bytestreams.icl Loading commit data...