Re: Problems with CAsyncSocket::Receive
TonyG wrote:
My version of OnReceive only calls Receive once. My code uses zero as the
first parameter to Create.
I double checked my code and found that it is not handling error conditions
when calling "Connect". My code assumed there was no error. Question? Can
Connect really generate a WSAEWOULDBLOCK?
Of course it can.
I don't understand what you mean by the new/delete mentioned in your post.
CAsyncSocket uses virtual functions. That means that my implementation must
derive from CAsyncSocket. So is your recomendation that my code support
dynamically allocating and deleting my derived class?
Yes, deleting your object after the disconnect gets rid of some stuff
you don't want hanging around.
Also...
It has always been my practice that when my TCP client class encounters a
closed connection (for any reason), I purposely wait 5 seconds before I
attempt a reconnect. What do other programmers do? I guess I implemented a 5
second wait because I didn't want my computer to get is some loop where it
attempts a connection a zillion times per second. Maybe my worries are
unfounded? Please enlighten me.
The old closed socket hangs around in some kind of dead state for
minutes. 5 seconds will not solve this annoyance. Creating a new
socket, with a new local port number, will connect rapidly. Any connect
attempt can fail, so I generally have a retry running on a 1-2 second timer.
--
Scott McPhillips [VC++ MVP]