[Ns-developers] NS-3 sockets data sent callback, again

George Riley riley at ece.gatech.edu
Wed Feb 6 07:22:15 PST 2008


Hi Gustavo,
I understand your point.  Why don't we specify two callbacks, one
that is called when the sockets "send" would return to the caller
(which is what you are asking for) and another one that is called
when the data is actually sent by the interface?  I can see a use for
both.

George
--------------------------------------------------
George Riley
Associate Professor
Georgia Tech
Electrical and Computer Engineering
riley at ece.gatech.edu

ECE4110 Web page:
http://users.ece.gatech.edu/~riley/ece4110/

ECE4112 Web page:
http://users.ece.gatech.edu/~riley/ece4112/





On Feb 6, 2008, at 10:18 AM, Gustavo Carneiro wrote:

>  I'd like to draw attention to
> http://www.nsnam.org/bugzilla/show_bug.cgi?id=131#c2
>
>  I had already discussed that the "output callback" in NS-3 sockets  
> is not
> in conformance with the BSD sockets interface.  IIRC the responses  
> at the
> time were like "NS-3 interface is simplified".  As I already  
> suspected back
> then, this interface makes life more complicated, not easier, and I  
> request
> reevaluation of the output callback interface.  In my opinion it  
> really
> should stick to BSD socket semantics, i.e., the output callback  
> should be
> called when the socket has buffer space available to accept more  
> data from
> the application, not when some data has been sent.
>
> -- 
> Gustavo J. A. M. Carneiro
> INESC Porto, Telecommunications and Multimedia Unit
> "The universe is always one step beyond logic." -- Frank Herbert



More information about the Ns-developers mailing list