Hello wayne,
if your socket is attached to a thread and multithread is true then all
events will fire in the same thread context. after OnSessionClosed is
fired (with or without error) you should not send data after it.
I think it is also a good idea to put all send operations in an
exception blo
Thank you Wilfried,
I think I have found the Problem, but still not sure what to "Check" for,
I did a Stack Trace:
First event is 10053 : Socket Disconnected, then because I was sending Data,
this code then continues to be executed:
size := Swap4(DataStream.Size);
Hello wayne,
Yes you probably access an object that never has created, or there is
some pointer overwritten. When you have the exception view the call
stack window to go to the offending code.
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
W
I have an Access Violation at address 0, I googled on this and found
that this means a reference to a null.
Basically I have implemented my Application based on "ThrdSrvV2_1" demo
project,
The problem happens as Follows: The Client connects to the Server, then
requests data,
I then Close the
