[Ns-bugs] [Bug 244] PacketSink is not multitasking

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

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


raj.b at gatech.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #191 is|0                           |1
           obsolete|                            |




------- Comment #5 from raj.b at gatech.edu  2008-07-03 11:57 -------
Created an attachment (id=193)
 --> (http://www.nsnam.org/bugzilla/attachment.cgi?id=193&action=view)
updated fix with extra documentation

This patch is against the latest ns-3-dev (post bug 243 patch) and adds some
comments to clarify how the sink operates in regards to its multiple sockets.

(In reply to comment #4)
[snip]
> Can you please create an example where more than one flow terminates on the
> same packet sink, and verify that all sockets (including the listening) are
> closed?

I think that attachment 190 or the new examples/tcp-star-server.cc will suffice
for this test case?  What remains to be checked is if the listening socket ever
"closes" under the current TCP code, and I'm kind of unclear as to what this
would mean in terms of socket behavior and memory management, i.e. what happens
(if anything) in terms of TCP when this happens, and should the closed socket
get deleted eventually as a result?


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