>I finally found the problem. In OnDataAvailable, in one of
> the cases Receive() did not read all the available data.
I'm happy you found the problem !
> Just to add a bit to the description of the problem - the
> problem only happens when wsoNoReceiveLoop is used.
Wehn wsoNoReceiveLoop is used
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
Thanks Francois and Wilfried for the replies.
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.
--
Best regards,
Jack
Sunday, December 31, 2006, 12:59:40 AM, you wrote:
>> So, my q
In addition it also has a nice side effect. When it is set and you dont
want to receive for a while then just dont receive in OnDataAvailable.
Then from that moment OnDataAvailable will not fire until Receive is
called once again.
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/te
> So, my question is, what is wsoNoReceiveLoop for
wsoNoReceiveLoop tell the component to not loop until the message queue has
no more FD_READ messages. When a loop is done (default) the component
receive data as fast as possible. This maybe result is heavy load on the
computer when the network
