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

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

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





------- Comment #5 from raj.b at gatech.edu  2008-02-12 10:00 -------
(In reply to comment #4)
> 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.
> 
Our TCP sockets DO fork now whenever a SYN packet arrives.  I'm not sure if I
made this clear or not in the original post, but what is in
http://code.nsnam.org/raj/ns-3-dev forks the socket and returns it to the
application via a call to NotifyNewConnectionCreated.  The original server
socket keeps on listening for incoming SYNs.  I'm not sure I understand what
the two issues are?


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