[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] socket close

From: yueyue papa
Subject: Re: [lwip-users] socket close
Date: Tue, 20 Apr 2010 20:22:22 +0800

I known the RST is not a stand solution, because it break TCP close spec.

Why I like to use RST is the standard close is a little slow. Takes a
little more time and inner timer resource. In the embedded
environment, I tried to as quick as possible. The RST to close make
the TCP close very quick, and clean. There is no inner resource
(timer) to maintain.

On Tue, Apr 20, 2010 at 6:49 PM, Kieran Mansley <address@hidden> wrote:
> On Tue, 2010-04-20 at 18:35 +0800, yueyue papa wrote:
>> I found some TCP/IP stacks use RST as close solution.
>> IwIP is use FIN, ACK as a socket close solution.
>> Could I choose RST solution for close socket?
> I regard using a RST to close a connection in the normal case as
> breaking the TCP spec.  There is a FIN/ACK sequence, and the TIME_WAIT
> state (which is what the stack's that are using RST are trying to avoid)
> for good reasons.  We re-use connections from TIME_WAIT if there aren't
> enough available, so this should remove the need to close connections
> with RST.
> So the short answer is "no", sorry.  Can you explain why you want to
> close connections with a RST?
> Kieran
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users

reply via email to

[Prev in Thread] Current Thread [Next in Thread]