[Ns-bugs] [Bug 205] socket API documentation is unclear about close callback semantics

[bugzilla-daemon@nsnam-www.ece.gatech.edu]

http://www.nsnam.org/bugzilla/show_bug.cgi?id=205





------- Comment #3 from mathieu.lacage at sophia.inria.fr  2008-06-05 12:36 -------
(In reply to comment #2)
> I agree with your reasoning, but I am also curious why these callbacks are
> tacked onto Connect and Accept callback setting routines.   Shouldn't this be
> split into a separate method (SetHalfCloseRequestedCallback())?

1) I am not suggesting we use any kind of accept callback here
2) it makes sense to associate the half close callback to the connect callback
method because half close events will never happen if you are not connected.
So, if you want to connect, you must set all callbacks which are related to
keeping track of the connection status.

I don't care much if you want to move that callback to a separate method but I
see a decent rationale for leaving it with the other connect callbacks.


-- 
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.