[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
Sun Feb 10 21:11:31 PST 2008


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





------- Comment #4 from tomh at tomh.org  2008-02-11 00:11 -------
I think there are two issues; a simple one and a harder one.  The simple one is
to simply fix the behavior for a non-multitasking server.  This should be
fixable with minimal effort (Gustavo's initial comment).

The second one is the multitasking server.  Here, there may need to be more
work done because tcp-full-duplex.cc (or any of our applications) do not even
handle the forking sockets because they themselves do not fork.

So I'd suggest to fix this one immediately without waiting to finalize the
forking server case.


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