MFTP port to ns-2

[Christoph Haenle <chris@cs.vu.nl>]

Hi Kannan,

thanks for your response. We decided to adopt option (b) for the meanwhile. 
I've just upgraded MFTP to the most recent version of ns-2 (there were 
virtually no changes to our code) and am about to review and document our 
extension package. I'll provide the ns-2 team (in January) with a brief manual 
that gives a description of the MFTP features for use within ns-2 and that 
explains the idea of the XOR-based erasure correction, which I had integrated 
into MFTP. Finally, I'd like to ask you to set a link to the web-page where 
all the stuff can be found (http://www.cs.vu.nl/~chris/Thesis/mftp/mftp_readme.
html). But please wait until January still.


   Greetings,

       -Christoph.



> Hi Christoph,
> 
> It is great to have other people's developing code into the core of ns.
> There are two modes in which we can use your work:
> 
> 	a)  You put your sources on the web, and we add a pointer to it
> 	    on the ns-contributed code pages.  In this mode, you can 
> 	    provide the patches for items 1 through 4 directly for people
> 	    to use.
> 
> or alternately,
> 
> 	b)  we can add it as part of the distribution.  You would be
> 	    nominally responsible for questions or bugs related to your
> 	    code.  If you have mods at a later date, you could send
> 	    us patches, and we will batch and apply them periodically.
> 	    In this case, you should send us a tar file with your sources,
> 	    as well as patches (source code diffs) to existing files.
> 	    A nominal README would be nice, as is an example of how to
> 	    use your modules in user scripts.  Further optional (but
> 	    useful) extras are validation tests/documentation of your code.
> 
> Thanks for your contribution,
> 
> 
> Kannan (for the VINT/ns developers team)
> 
> PS:  As for the RM code, it looks like I'd be the stuckey responsible
> for integrating into ns.  If so, I'd like to wait until mid-January.
> I trust that will be ok with you? -- Thanks.