[Ns-developers] Cooperative ns-3 simulation with third party software via JSON-RPC

[Sébastien Vincent]

Sébastien Vincent wrote:
> Hi Mathieu,
>
> Mathieu Lacage wrote:
>> On Mon, 2009-01-12 at 13:34 +0100, Sébastien Vincent wrote:
>>
>>  
>>> OK so we wait your comments. And later we could discuss about 
>>> merging it, maybe for ns-3.[45].
>>>     
>>
>> Can you point me to the list of new/modified files ?
>>
>> Mathieu
>>
>>

I forgot some files:

src/example/rpc-synchronisation.cc
src/example/rpc-simulation.cc
src/example/rpc-udp-echo.cc
src/example/wscript (modified)

src/mobility/rpc-mobility-model.cc,h
src/mobility/wscript (modified)

src/helper/rpc-udp-echo-helper.cc,h
src/helper/wscript (modified)

>>   
>
> New files:
>
> README.JsonRpc
>
> src/rpc-agent/ns-3-rpc-server.cc,h
> src/rpc-agent/rpc-agent.cc,h
> src/rpc-agent/synchronisation-agent.cc,h
> src/rpc-agent/update-agent.cc,h
> src/rpc-agent/wscript
>
> src/rpc-applications/rpc-application.cc,h
> src/rpc-applications/rpc-udp-echo/rpc-udp-echo-client.cc,h
> src/rpc-applications/rpc-udp-echo/rpc-udp-echo-server.cc,h
> src/rpc-applications/rpc-udp-echo/wscript
>
> Modified files:
>
> src/node/socket.cc,h => SourceSocketAddressTag class
> Note that this can be avoided by adding two SocketAddressTag (one for 
> destination and one for source address) and know at the application 
> level which is source and which is destination.
>
> src/internet-stack/udp-l4-protocol.cc => add a SourceSocketAddressTag 
> tag in the packet (::Receive())
> The same modification should be done for tcp-l4-protocol.cc to allow 
> an "rpc-tcp-echo-server/client" like to be implemented.
>
> src/wscript => add modules (rpc-agent, rpc-applications and 
> rpc-applications/rpc-udp-echo)
>
> wscript => Add link to libjson and libjsonrpc
>
> Regards,
> -- 
> Seb
>
>