It's UWAweek 17 (1st semester, week 8)

help3002

This forum is provided to promote discussion amongst students enrolled in CITS3002 Computer Networks.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message. How do I ask a good question?

Displaying selected article
Showing 1 of 248 articles.
Currently 2 other people reading this forum.


 UWA week 14 (1st semester, non-teaching week) ↓
SVG not supported

Login to reply

👍?
helpful
11:15pm Thu 4th Apr, ANONYMOUS

Hello, I was looking at the solutions for the piggybacking implementation of Lab3 Q1 and I noticed that something I thought had to be implemented isn't there. So with piggybacking, the piggybacking timer begins when data is received, waiting to see if the ackowledgement frame can be sent in the same frame as the next data frame, which will be sent from the receiver. My understanding was that the piggybacking timer needs to be stopped if piggybacking does in fact occur. Say we have two ends A and B. If B is able to piggyback an acknowledgement onto data it is sending to A, then it is transmitting the current ack_pending value as ack_seq. When A receives this, given that it has received data, it will do ack_pending = f.data_seq (line 134 of the solutions I think) so the ack_pending value changes. If the piggyback timer is not stopped after this happens, it seems that it will still transmit the old acknowledgement frame with the old ack_pending number. (Or maybe instead of stopping the timer we can check if the ack_pending value is the same as the one when the timer began and then transmit the ack frame if the value is the same?) Am I perhaps misunderstanding something in the code or concept of piggybacking, or is this a missing feature?

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  5:07AM Sep 06 2023
Privacy policy