Asynchronous Socket Problem with TCPIP

[DaTurk]

Hi,
Lets see, for arguements sake lets just say that I have a server,
which site waiting to receive connections, it then has an array of
sockets that are connected to it.

It's receiving all of this asynchronously. Now, this is my problem, I
have a seperate application that connects to the server and can
disconnect any of the sockets connected to it. But, lets just say I
have one client connected, and then I attempt to disconnect them via
the seperate application. I close the socket, and remove it from the
array on the server, but then the server receives a message from the
client where their socket is equal to null. Does anyone know how this
is possible?

 

[Chris Mullins]

When your socket closes, any asynchronous operations that happen are
terminated.

This means the callback you passed to BeginReceive will fire, you'll call
"EndReceive", and gracefully handle your shutdown conditions from there.