I finally found the problem. In OnDataAvailable, in one of
the cases Receive() did not read all the available data.
===8<==Original message text===
Just to add a bit to the description of the problem - the
problem only happens when wsoNoReceiveLoop is used.
--
To unsub
Just to add a bit to the description of the problem - the
problem only happens when wsoNoReceiveLoop is used.
- The connection is not closed but there's no data coming in.
This typically happens after a few MByte of data has been
transferred.
- I log Pause and Resume calls so that I see th
Hi Francois,
> As far as I know, "TCP zero window" is sent when the comiter is not able to
> receive data anymore because the receive buffer is full. And still as far as
> I know this is not an error if it doesn't persist for too long. It is simply
> part of the control flow in TCP protocol.
> Sp
> I still have no clue why it's causing TCP stack to send
> TCP zero window to the server... basically when the zero
> window packet shows up, the connection will break.
As far as I know, "TCP zero window" is sent when the comiter is not able to
receive data anymore because the receive buffer is
