[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] tcp_close() in callback API
From: |
Kjell Andersson XW (LI/EAB) |
Subject: |
[lwip-devel] tcp_close() in callback API |
Date: |
Tue, 9 Dec 2003 09:14:57 +0100 |
When using the callback API of lwIP, using the stack against itself and one of
the sides does a tcp_close(), how is the other side supposed to get informed
that it too should tcp_close()? Under normal circumstances, in a non callback
API, the non closing side would get an EOF when reading from the connection but
in a callback case no such reads are done. Shouldn't there be some callback
notification in the ESTABLISHED case in tcp_process before going to the
CLOSE_WAIT state?
As it is today, using the callback API, a connection has no way of telling if
the connection was closed.
- [lwip-devel] tcp_close() in callback API,
Kjell Andersson XW (LI/EAB) <=