Date: Wed, 30 Jul 1997 13:47:06 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: marcs@znep.com (Marc Slemko) Cc: terry@lambert.org, freebsd-current@FreeBSD.ORG Subject: Re: Who is working on the TCP stack? Message-ID: <199707302047.NAA05810@phaeton.artisoft.com> In-Reply-To: <Pine.BSF.3.95.970730132848.19785J-100000@alive.znep.com> from "Marc Slemko" at Jul 30, 97 01:34:16 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > The problem is that the client applications, specifically the > > nono-Internet Explorer applications, do not call the WinSock > > function "shutdown( s, 3);" and then "recv( s, ...);" all > > the packets until the remote side close the connection. > > Erm... no. That has absolutely nothing to do with this issue. > This particular issue is a disagreement in the slow-start > implementation. Slow-start is documented after-the-fact in RFC2001 > for anyone interested. > > The difference revolves around who should send what when; one box > is expecting the other to send something, the other is expecting > the first to send something, so they deadlock until one times out > and retramsmits. Don't have the exact details offhand and I don't > know if FreeBSD is impacted. I have never heard of this one, actually. I do know for a fact that you can end up with thousands of sockets in "WAIT FIN" with MS clients, effectively locking up UNIX servers. I guess this is just another toy surprise in a long line of toy surprises... 8-|. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707302047.NAA05810>