Silly Window Syndrome

Question

Answer 1

Answer is (C) I, II and III.

Silly Window Syndrome is a case of poor TCP flow control. It may arise out of three circumstances:

1. When a server is unable to handle client data, it requests the client to lower the window size, so that the flow is acceptable to the server. As time progresses, the server finds it still unmanageable, so again requests the client to lower the window size. Finally, a situation reaches when the actual data transferred is even less than the header size, after which transmission is extremely inefficient. Beyond this, the server "announces" a 0 empty window space, leading to Silly Window Syndrome.
2. It may also be the case that the application program may create data slowly, so that at any time, there aren't enough bytes to fill a big window. As a result, a small (silly) window is preferred.
3. Also, the server may consume (or process) only 1 byte at a time, leading to extremely uneconomical data transmission. A Silly Window may be agreed upon by both parties.

So all the three cases lead to Silly Window Syndrome.

Comments

Iam agree with your 2nd and 3rd point and I am only aware about these two cases.But as per your point 1 it is the general case of flow control.Is it also a type of silly window syndrome? I think during SWS server can consume 1 Byte data only at a time.So it must announce only 1 empty window space.