[Top][All Lists]

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

Re: [lwip-devel] [bug #51789] TCP_EVENT_CLOSE, tcp_close() and possible

From: address@hidden
Subject: Re: [lwip-devel] [bug #51789] TCP_EVENT_CLOSE, tcp_close() and possible use of pcb with tcp_output()
Date: Mon, 28 Aug 2017 19:47:59 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0

Art Heers wrote:
Follow-up Comment #6, bug #51789 (project lwip):
Maybe I can change the discussion here by asking why call tcp_close() inside
the call back function?

No, please don't hijack closed bug entries for discussions. Continuing on the list.

It looks like the LwIP stack takes care of the
closing process without the call back function calling tcp_close().

No. Maybe you should dive deeper into TCP (again?): TCP provides a full-duplex communication channel where both sides may close there TX end when they whish (unless a RST is received). So you get the NULL pbuf when receiving a FIN, but that won't result in your side sending a FIN. That will only happen if you call tcp_close().


reply via email to

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