Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Dave Korn" <dk AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: pthreads and sockets - Cannot register window class error
Date: Wed, 5 May 2004 12:47:49 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <BAY9-F6gmkLGeq3v7dq00002682@hotmail.com>
Message-ID: <NUTMEGWdBdsnvUFcxT50000019f@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 05 May 2004 11:47:49.0296 (UTC) FILETIME=[CA410B00:01C43296]

> -----Original Message-----
> From: cygwin-owner On Behalf Of Arash Partow
> Sent: 05 May 2004 12:04


> I can't replicate your problem, but I know where it is coming from,
> basically standard windows winsock is not geared up to handle that man
> socket connections. When a socket is made and then closed the socket
> actually stays open for about 240-300 seconds depending on your
> registry settings, this is so that winsock can make sure the
> connection has been properly closed off.

> or just  simply use *bsd or linux tcp/ip stack.


  Nope, that won't help, unless of course it's because *bsd/linux already
have their stacks tuned for server-like applications by default.  This delay
isn't a windoze-specific feature, it's a generic and universal feature of
all TCP/IP implementations: google for "TIME_WAIT" and "2MSL" and read RFC
793 to find out more, also 

http://www.developerweb.net/sock-faq/detail.php?id=13


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/