On Mar 26, 2010, at 04:02, Jon Robertson wrote:
> To clarify, OnDataAvailable has received complete data, say:
> help\n
>
> In processing that data, an exception occurs and TWSocket.Abort is called to
> abort the connection. Before .Abort returns, OnDataAvailable is called
> again, with the exact same that was already being processed:
> help\n
>
> But the client has only sent the data once.
Oh, I see. The Abort method calls OnDataAvailable because the even was never
completely handled, and thus the component still thinks the received data is
available.
I'm not sure how this could be handled in the component.
I'm using a Mac at this moment so I cannot test this. Can you show me the call
stack of when the second OnDataAvailable is triggered? I can't seem to find an
obvious execution flow in the code (it's very early still).
dZ.
--
DZ-Jay [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
