From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id IAA02168 for caml-redistribution; Fri, 11 Sep 1998 08:42:51 +0200 (MET DST) Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id AAA25928 for ; Fri, 11 Sep 1998 00:23:37 +0200 (MET DST) Received: from cs.Technion.AC.IL (csa.cs.technion.ac.il [132.68.32.1]) by nez-perce.inria.fr (8.8.7/8.8.7) with ESMTP id AAA01371 for ; Fri, 11 Sep 1998 00:23:33 +0200 (MET DST) Received: from localhost (roy@localhost) by cs.Technion.AC.IL (8.9.0/8.9.0) with SMTP id AAA20374 for ; Fri, 11 Sep 1998 00:23:29 +0200 (IST) Date: Fri, 11 Sep 1998 00:23:29 +0200 (IST) From: Friedman Roy X-Sender: roy@csa To: caml-list@inria.fr Subject: socket in the windows port Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: weis 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