lwip-devel
[Top][All Lists]
Advanced

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

[lwip-devel] [task #10088] Correctly implement close() vs. shutdown()


From: Simon Goldschmidt
Subject: [lwip-devel] [task #10088] Correctly implement close() vs. shutdown()
Date: Tue, 16 Feb 2010 16:18:34 +0000
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.2) Gecko/20100115 Firefox/3.6

Follow-up Comment #9, task #10088 (project lwip):

OK but when using tcp_recved(), we couldn't differ between raw API- and
netconn/socket-applications. Therefore, I think it would be OK to require raw
API apps to call tcp_recved before calling tcp_close - unless they don't care
for the RST.

> There is no buffering in the raw API.

There is struct tcp_pcb.refused_data...

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?10088>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/





reply via email to

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