Ok, I know what the second problem is, it seems that the packet complete right after you close the socket making the callback get called again, I guess I just need a way to keep track of this last event.
Yeah, my IOCP objects keep track of how many other IOCP calls are waiting to complete.  As long as that number is greater than 0 the object is not deleted (from memory).
 
And when you close a socket all the outstanding IOs are immediately "canceled" and come back as NULL read/write, so make sure you handle that case correctly.
I have found one more thing though....  The server seems to receive/send the packet server times in succession and I'm not sure why.....  Something for me to look in to I guess.
I'm not sure I understand the issue here.
 
/dev

Reply via email to