Re: [ns] BayFullTCP vs. FullTCP

[Padmaparna Haldar <haldar@ISI.EDU>]

BayFullTcp and FullTcp are two different implementations of the same
two-way tcp. While the latter is what we had in ns, the former was ported
into ns from Kathy Nicholes/Van Jacobson's grp.
The basic differences between the two being that
* baytcp supports a client-server application model while fulltcp makes
no assumption about its application layer.
* Also tcp-application interface is different for both;
* baytcp supports partial ack (fulltcp doesn't).
* fulltcp supports different flavors of tcp (tahoe, reno etc)
which is not the case for baytcp.
* both implementations have different set of API's .
There might be other finer differences between the two as well.

One of our future plans is to redefine the APIs to allow fulltcp to use
baytcp's client-server model.

Thanks,
--Padma


On Thu, 7 Jun 2001, Michele Clark Weigle wrote:


>  Can someone give us a brief overview of the differences between
> BayFullTCP and FullTCP?
>
> Thanks,
> Michele
> --
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> Michele Clark Weigle                        michele_weigle@unc.edu,
> CB# 3175, Sitterson Hall	            clark@cs.unc.edu
> Department of Computer Science		    http://www.cs.unc.edu/~clark
> University of North Carolina		    Sitterson 327
> Chapel Hill, NC 27599-3175                  (919) 962-1909
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>

-- 
------------------------------------------------
Be true to your work, your word, and your friend.
--Thoreau

Padmaparna Haldar