Re: Deaf CAsyncSocket on Windows Service.

I agree that CAsynSocket must work otherwise networking, Internet Explorer,
the Internet, etc. would all be unreliable.

The problem is that I don't see anything in the callback that I believe
would be pumping messages. Basically the callback just gets a CString from
my derived class and pushes (AddHead) it into a CList to be checked and
pulled out later by another part of the program. We don't process the
CString immediately in the callback. The program is multithreaded but I
don't know if any other thread is doing any message pumping or if that
would even cause a problem to the socket in its thread.

If so, wouldn't I still expect to see the failure when I do only one
Receive() per OnReceive()? And if not, what else could be causing the
error when I do more than one Receive() in OnReceive()?

I did just test for double entry into OnReceive() while I had restored the
loop that calls Receive() more than one per OnReceive(). The problem
occurs but there was no double entry into OnReceive(). I kept the receive
buffer purposely short to guarantee that there was always more than one
Receive() per OnReceive().

Thanks...