Re: tcp-www.cc

[kpoduri@BayNetworks.COM (Kedarnath Poduri)]

Hi Deniz,
	If the model is developed based on the earlier tcp version of ns, i.e. 
not
the full-tcp that is being shipped with the latest version, then the connections
are handled one way. In the earlier version of tcp, there is a source and a 
sink. source generates the data packets while the sink generates ONLY acks. 
Its essentially one way traffic. But Emile should be able to give you more 
details.
	We have a model of HTTTP (1.0 & 1.1) built on a full-tcp (our own 
version developed by kathie nichols (knichols@baynetworks.com), where all
the 'communication details are present'. We would be putting up all the relevant 
files at some site in LBL in a couple of days. You can have a look at them.

kedar


> 
> I have included the tcp-www.cc into ns, and recompiled it successfully.
> But, I couldn't understand the features of tcp-www.cc exactly. 
> 
> For example, what does the callback function do? In the README file for
> the implementation written by Emile Sahouria it is written that: "The
> derived class Agent/TCP/WWW provides a callback when a TCP connection
> completes."  Is the implementation imitates a persistent connection HTTP
> with this feature? 
> 
> Secondly, I couldn't understand why the connections are handled as one-way
> in the output trace files. Since the 3-way handshake takes place between
> the server and the client, there should be a two way traffic? Maybe it is
> because of simplicity constraints. But, please let me know if so.. Because
> I will probably need the whole communication details in my simulations.
> 
> Thanks in advance..
> Sincerely,
> 
> Deniz GURKAN
> e-mail: deniz@ee.bilkent.edu.tr  URL: http://www.ee.bilkent.edu.tr/~deniz/
>