Re: [lwip-users] TCP keep alive info to the application

[Joel Cunningham]

Agreed, trying to leverage TCP keepalive information in the application level is incorrect.  The keepalives are used internally by TCP and will abort the connection when communication is lost.  This event is then typically communicated through socket APIs returning an error on next use.

You most likely need an application level heartbeat/keepalive. See this article for information about detecting half-open (stale/dead) connections: http://www.codeproject.com/Articles/37490/Detection-of-Half-Open-Dropped-TCP-IP-Socket-Conne

Joel

On May 30, 2016, at 07:49 AM, "Sergio R. Caprile" <address@hidden> wrote:

Playing the role of the pedantic teacher here, what you want to do
violates the allmighty layer independence of the OSI model. Before the
ISO police comes after you in the form of many unexpected problems, I
suggest you implement your own in-application keep-alive mechanism. Been
there.

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users