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

[Jeff Barber]

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

I agree that, for native API apps, close is completely equivalent to
shutdown(SHUT_RDWR).  In a standard BSD sockets implementation, the two should
be equivalent with respect to the protocol stack; the only significant
difference is that close also deallocates the socket file descriptor.

Not really sure about how SHUT_RD should work but as far as I can tell,
neither is anyone else.  :-)  I don't think it matters; the consensus seems to
be that SHUT_RD alone is ill-defined and really doesn't make a lot of sense.

If I understand your last point, you're referring to the API change (current
caller of tcp_close would require code change to tcp_shutdown(WR) because
tcp_close gets different behavior)?  If so, I agree that it's a major change
but also think that it's the right thing to do.  It would certainly deserve a
big fat note in the 1.4 readme.


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/