The following code snippet fails to open a socket when non-blocking is enabled, but works with it commented out (as below).

Is this a finger trouble thing, or a feature of the TCP/IP stack in Windows XP Pro?

I also don't quite understand why the "socket open" has to specify blocking or non-blocking; I would have expected to be able to specify blocking or non-blocking for individual reads from the socket.

TIA

Dave R

while (1) {

    #-----------------------------------------------------------------
+--
    # Connect via a socket to the server
    #-----------------------------------------------------------------
+--
    
    logmsg "Creating a socket on host $remote_host, port $port";
    
    my $sock = new IO::Socket::INET( 
    
        'PeerAddr'    => $remote_host,
        'PeerPort'    => $port,
        'Proto'        => 'tcp',
        'Type'        => SOCK_STREAM,
#        'Blocking'    => 0,    # hope this override default use of Na
+gle algorithm
    );
    die "Socket could not be created to host $remote_host, port $port.
+  (Do you mean to run with '-i localhost' ?)  Reason: $ERRNO" unless 
+$sock;
[download]