[Ns-developers] [ns3] socket API

[George Riley]

>
>>>
>>>
>>
>> The larger issue here seems to be what will be the prevailing model  
>> for
>> applications that we will use as examples of how to do things in  
>> ns-3? I'm
>> not sure that many people have looked closely at Mathieu's ns-3- 
>> simu but one
>> possibility would be that the process code (see examples/ 
>> process.cc) would
>> be the most widely used API,
>
>
> See, this is what I was afraid of.  You are opening the door for any  
> and
> every simulation model to use simulated processes, yet the performance
> implications of this approach have not been studied.  We have  
> already seen
> that the only portable implementation of simulated processes is  
> through
> POSIX threads, namely one thread per simulated process.  Now suppose  
> you
> have 500 nodes, each running 2 routing protocols using synchronous  
> socket
> API.  NS-3 will then create 1000 threads.  And what will the  
> performance of
> that look like?...
HI Gustavo,
I don't think Tom is suggesting that we would drop the so-called  
asynchronous
API; rather he thinks the process-based one might be more popular.   
Whether
or not this is comes about does not seem significant at the moment.   
I'm very
much with you, that performance will suffer if a user models 10,000  
peer-to-peer
applications, each with a separate thread and private stack.  Anyway,  
rest
assured the async approach is and will remain an integral part of  
ns-3, and
in my opinion the method of choice for most users.

George