This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: pthreads and sockets - Cannot register window class error
- From: "Dave Korn" <dk at artimi dot com>
- To: <cygwin at cygwin dot com>
- Date: Wed, 5 May 2004 12:47:49 +0100
- Subject: RE: pthreads and sockets - Cannot register window class error
> -----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/