How do we prevent the sender from flooding the receiver with data faster than the receiver is able to process it?
There are two levels to this question. We have been considering data-link issues where two nodes (switches, routers, directly connected hosts, sender/receiver on a Ethernet) are managing a direct link connection. They are attached to a channel of the same bandwidth and using the same protocols to manage this channel. The data link protocol will specify a maximum frame size and a window size for sender and receiver that the switches will be capable of handling. The only recourse that the receiver has when faced with congestion delays is to delay the return of ACKs and discard frames that it is not capable of buffering. This will cause the sender to timeout and retransmit those frames effectively slowing it down. Data link protocols seek to maximize the efficient use of the channel and try to avoid this eventuality. Your question anticipates the situation where machines of different capabilities, and possibly running different network protocols are connected through a network or an inter
Related Questions
- How do we prevent the sender from flooding the receiver with data faster than the receiver is able to process it?
- Why is it necessary to keep the transmission data about the sender, receiver, date and time of the e-mail?
- How can I make the selection process faster especially when xref data is included?
