From: Daniel Berger <djberg96@...>
Date: 2006-09-27T11:05:57+09:00
Subject: Re: RDoc patch, possible bug in socket.c for TCPSocket.new

------=_Part_17922_31334795.1159322753910
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 9/26/06, Francis Cianfrocca <garbagecat10@gmail.com> wrote:
>
> On 9/26/06, gwtmp01@mac.com <gwtmp01@mac.com> wrote:
> >
> >
> > This is the normal behavior for a TCP session.  After the server
> > sends the
> > final ACK to the client, the TCP session must remain in the TIME_WAIT
> > state
> > for twice the maximum segment lifetime.  The delay is to handle lost
> > acks,
> > or stray duplicate segments that arrive after the session has been
> > closed.  It
> > is the kernel that takes care of this housekeeping.
>
>
> A little more: TIME_WAIT is only incurred by the side of the connection
> that
> initiates the connection teardown. In your example, that would be the
> client-side. What surprises me about this example is that some kernels
> don't
> bother with TIME_WAIT when both client and server are localhost, because
> the
> kernel is in a position to know for sure whether any data belonging to the
> connection is still floating around. So I was also curious about the
> platform Daniel is running this on.
>
>
The platform is Solaris 10.

- Dan

------=_Part_17922_31334795.1159322753910--