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: Sat, 20 Feb 2010 18:13:30 +0000
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.2) Gecko/20100115 Firefox/3.6

Update of task #10088 (project lwip):

        Percent Complete:                      0% => 60%                    
             Assigned to:                    None => goldsimon              
         Planned Release:                    None => 1.4.0                  

    _______________________________________________________

Follow-up Comment #12:

I've just checked in something to get us started on this:
- tcp_shutdown(WR) does the same as the previous tcp_close,
- tcp_shutdown(RD) sets a flag TF_RXCLOSED
- if the flag is set, pcb->tmr is not updated on input segments (Fixes bug
#26062)
- if the flag is set, TCP_EVENT_RECV does *not* call the application's recv
callback but instead update the window accordingly

There are 3 open points:
- Is this the correct implementation of SHUT_RD?
- The above changes still process incoming data after FIN is sent, is this
OK?
- As written in last comment, SHUT_WR may lead to closing the connection too
early.

    _______________________________________________________

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]