[Ns-bugs] [Bug 132] TCP does not notify server side sockets of new connections

bugzilla-daemon@nsnam-www.ece.gatech.edu bugzilla-daemon at nsnam-www.ece.gatech.edu
Tue Feb 12 10:52:59 PST 2008


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





------- Comment #6 from raj.b at gatech.edu  2008-02-12 13:52 -------
Surprisingly, our current test cases with one sender and one packet-sink works
with the change to forked sockets.  The reason is that the packet sink
registers a receive callback with its listening socket.  When the listening
socket is forked, the copy constructor copies the callback as well, and then
invokes it upon data receipt, passing up to the application correctly.

More testing remains to be done to see if the behavior is correct for multiple
connections to one server.


-- 
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.


More information about the Ns-bugs mailing list