[Ns-bugs] [Bug 424] TCP FIN notification callback needed
code@nsnam.ece.gatech.edu
code at nsnam.ece.gatech.edu
Wed Mar 18 06:40:13 PDT 2009
http://www.nsnam.org/bugzilla/show_bug.cgi?id=424
--- Comment #4 from Tom Henderson <tomh at tomh.org> 2009-03-18 09:40:13 EDT ---
(In reply to comment #2)
> The inline docs say:
>
> """Sets the "close" callback, which is a notification
> that the other end of the connection has sent a message
> indicating that it will not send any more data, i.e.
> the socket is closed for reading."""
>
> While this may be true, I think it's even more important to note that, when the
> close callback is invoked we have a guaranteed that all data _we transmitted_
> has been flushed and acknowledged by the receiver.
We would need to be notified in this case of an ack of our FIN, or detection of
RSTs, which is not what this is doing.
It would help to clarify what we want to model; I can't really tell from the
initial bug report.
--
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the Ns-bugs
mailing list