Appendix 2: Incomplete Chuncks

                      

Home

Members

Project Design

Implementation Design

Simulation Results

Benefits and Drawbacks of our Project

Improvements, Applications And Related Work

Conclusion

References

Appendix 1: Java Security

Appendix 2: Incomplete Chunks

Appendix 3: Source Code

Demo: A Test Drive 

 




If we have a large file, it will probably occupy more than one chunk. It is also likely that the last chunk will be incomplete, containing fewer bytes than a normal chunk (for example 334,541 bytes). All the algorithms above assume that the chunk is complete (i.e, 32 strips of 32 packets each). How do we apply our algorithms to incomplete chunk?

 

First of all we pad the chunk to contain an integer number of packets. Second, the incomplete chunk contains fewer strips than a normal chunk. An incomplete chunk will contain some strips of 32 packets and at most one strip of less than 32 packets.

 

Suppose there is such strip and it contains 'k' packets. This strip will be encoded and decoded using special parameters. The interleaving of the strips will work as usual, until some point at which the incomplete strip stops and the interleaving continues without it. The ordering of "good" (not encoded) packets inside strips remains as normal for strips of the same number of packets (complete and incomplete).

 

Both the encoder and the decoder must carefully calculate all these indexes and placements.

 

Please contact Genady or Nir regarding copyright issues 
For problems or questions regarding this web contact the members.
Last updated: Wednesday, September 08, 1999.