AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Stop and wait arq8/4/2023 This declaration, and all other data structure and emulator routines, as well as stub routines (i.e., those you are to complete) are in the file, prog2.c, described later. The unit of data passed between the upper layers and your protocols is a message, which is declared as: The overall structure of the environment is shown in Figure Lab.3-1 (structure of the emulated environment): These procedures will be called by (and will call) procedures that I have written which emulate a network environment. Your routines are to be implemented in the form of the procedures described below. Of course, the B side will have to send packets to A to acknowledge (positively or negatively) receipt of data. Only unidirectional transfer of data (from A to B) is required. The procedures you will write are for the sending entity (A) and the receiving entity (B). Stopping/starting of timers are also simulated, and timer interrupts will cause your timer handling routine to be activated. (Indeed, the software interfaces described in this programming assignment are much more realistic that the infinite loop senders and receivers that many texts describe). However, the programming interface provided to your routines, i.e., the code that would call your entities from above and from below is very close to what is done in an actual UNIX environment. Since you probably don't have standalone machines (with an OS that you can modify), your code will have to execute in a simulated hardware/software environment. This lab should be fun since your implementation will differ very little from what would be required in a real-world situation. There are two versions of this lab, the Alternating-Bit-Protocol version and the Go-Back-N version. In this laboratory programming assignment, you will be writing the sending and receiving transport-level code for implementing a simple reliable data transfer protocol. Please do not use compiler specific instructions. printout of your section of the source code (only portion that you write, not the whole source code). an output which demonstrates at least 10 successfull frame transmissions A to B. brief description of the functions that you write In your report, Please include following in your report: there is an upper layer wch hands the packet down to A, A sends the packet thru a lower layer to B, and B in turn hands an error free packet back to the upper layer.The problem is that we've been given part of the code to folow and our final code must continue from there in other words our program must model around the given format, wch i ve found very difficult to understand. I have this code to turn in next 3 days it is simply supposed to be a sender A transmitting packets to a reciever B which in turn acknowledges it( or nack) it uses checksums and sequence and ack nos for error control.
0 Comments
Read More
Leave a Reply. |