🚀 go-pugleaf

"Martin" <dev@no.comppromed.spam.com> wrote in message
news:44298fd1$1@newsgroups.borland.com...

> No, it's not overwriting the surrounding memory. And the buffer is
> much bigger than the incoming packets.

That does not mean that the buffer is not filling up, if the application is
not removing data from the buffer faster than it arrives.

> During the timeframe where it's not working, they're sending and
> resending, but no response from us.

How are you verifying that, though?  Did you try using a packet sniffer to
make sure that data is actually reaching your machine?

> When it happened last night, I did not get any of
> the auditing statements from the read event. So
> either no events happened or the underlying recv()
> calls always returned 0.

recv() returns 0 when the socket has been disconnected by the other party.
If there is no data available but the connection is still active, then
recv() will return SOCKET_ERROR and WSAGetLastError() returns
WSAEWOULDBLOCK.

You should be using ReceiveLength() before ReceiveBuf() to make sure that
there is any data available for reading before you attempt to actually read
it.


Gambit