socket in the windows port

socket in the windows port

[Friedman Roy]

Hi everyone,

In looking at the code of socket.c for windows, I noticed the following
code:

  /* Set sockets to synchronous mode  */
  optionValue = SO_SYNCHRONOUS_NONALERT;
  setsockopt(INVALID_SOCKET, SOL_SOCKET, SO_OPENTYPE,
             (char *)&optionValue, sizeof(optionValue));

Is there a reason it is there? One negative aspect of this is that when
one tries to set a socket to a non blocking mode and then connect to it,
then NT returns a WSAEINVALID error code, meaning that the operation is
not allowed on that socket.

Thanks,

Roy

Re: socket in the windows port

[Xavier Leroy]

> In looking at the code of socket.c for windows, I noticed the following
> code:
>   /* Set sockets to synchronous mode  */
>   optionValue = SO_SYNCHRONOUS_NONALERT;
>   setsockopt(INVALID_SOCKET, SOL_SOCKET, SO_OPENTYPE,
>              (char *)&optionValue, sizeof(optionValue));
> Is there a reason it is there?

I'm not in front of my Windows development machine, so this is all
from memory.

My recollection is that setting the sockets to synchronous mode is
necessary if one wants to read and write from sockets using the
generic ReadFile and WriteFile system calls.  This is what the libunix
does, since it does not distinguish file handles and socket handles
(As per the Unix programming model).

> One negative aspect of this is that when
> one tries to set a socket to a non blocking mode and then connect to it,
> then NT returns a WSAEINVALID error code, meaning that the operation is
> not allowed on that socket.

I don't remember how "non-blocking mode" works under Windows.  At any
rate, couldn't you just use blocking I/O operations in several threads
instead?

Regards,

- Xavier Leroy