Very good for a refresher as this explanation is easy to digest and has good examples. Thanks for putting this together

Simple and nice explanation. Thanks!!

Precise Teaching. Loved it!

Easy to digest writing style with helpful images. Wonderful write up shedding light on a critical TCP topic. Thank you for writing this and contributing your knowledge. Might have to look into your kubernetes book!

Thanks for sharing, really good summary!

cool！

i think one of the best article in TCP flow control, very easy to understand

Execellent write up..couldn't find a better writing than this..

Thx

Really Helpful, Thanks for sharing.

Excellent Writing, Really Helpful

Excelent! exactly what I was looking for.

Thanks for sharing!

Good Article, one question. Here we assume that the node B advertises a receive window of 45000 bytes initially, is that the case in real tcp connection? does it really notify the sender about the window size before the data transfer starts?

Yes, during so called three way handshake both server and client exchange the information about the their windows sizes, usually client has larger window size than server, as in most cases server serves the data to the client

This is a wonderful article. Thank you for sharing it.

Cool!!!

Very Nice explanation, thanks

Pure Gold, Thank You.

Great article! I have one question though: When there are more than two participants in the game, e.g. a loadbalancer or proxy between the client and the server, how does flow control change? I would assume the client talking to the LB will see its receive window while the LB will see the backend server's window. So when the client keeps pushing more data to the LB, eventually the server will advertise a zero window to the LB, right? Does the LB pass this information on to the client? I think it will instead fill up its own receive and send buffers and only advertise if those are full. Could you shed some light here, please? Thank you so much.

Your description of what happens in this situation is quite accurate.

This was very straight forward and easy to read. Thank you.

wow

What a beautiful article

Great article, Many thanks to you.
Could you let me know which was the language used to write client/receive program.

Thanks for writing :)

Great article! Well written and easy to understand. Thanks!

I agree w/ all the other commenters, this was a truly excellent article that explained TCP flow control clearly and in an engaging and easy to understand way.

great explanation, first class work!

Simple, well-written and very informative. Thanks.

One of the best posts I've seen on the Flow Control in TCP anywhere. Great illustration graphics. Thanks.

Awesome article on flow control

Hey Brain,

Thanks for this article! Your clear description and explanation really helped me a lot with understanding the flow control in TCP!

Thank you!

Amazing article!

Nice explanation!

(y)

Simple and clear explanation. Perfect! Thank you.