[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [task #10088] Sockets: Correctly implement close() vs. shut
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [task #10088] Sockets: Correctly implement close() vs. shutdown() |
Date: |
Mon, 11 Jan 2010 16:43:33 +0000 |
User-agent: |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 |
URL:
<http://savannah.nongnu.org/task/?10088>
Summary: Sockets: Correctly implement close() vs. shutdown()
Project: lwIP - A Lightweight TCP/IP stack
Submitted by: goldsimon
Submitted on: Mo 11 Jan 2010 16:43:33 GMT
Category: None
Should Start On: Mo 11 Jan 2010 00:00:00 GMT
Should be Finished on: Mo 11 Jan 2010 00:00:00 GMT
Priority: 5 - Normal
Status: None
Privacy: Public
Percent Complete: 0%
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
Effort: 0.00
_______________________________________________________
Details:
This has come up in bug #26672 (close connection when receive window = 0) and
bug #24830 (Socket never closed sometimes):
The current implementation of close() is shutdown(), really. We currently
don't have a close(), which sends RST when data arrives after calling it.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/task/?10088>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [lwip-devel] [task #10088] Sockets: Correctly implement close() vs. shutdown(),
Simon Goldschmidt <=