]
http://www.overbyte.be
- Original Message -
From: Wilfried Mestdagh [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Saturday, April 14, 2007 6:13 PM
Subject: Re: [twsocket] Client close exception and connection doubt
Hello Éric,
The exception that was raised
Hello Éric,
The exception that was raised was Socket operation on non-socket (#10038 in
Possible the socket was already destroyed. Other possibility is that
somewhere some pointer is pointing wrong or is been overwritten. Very
difficult to say.
came to see on the morning the whole windows
Hello all,
I want to discuss an architectural issue here
I´m debugging an application of mine and yesterday it has stopped working and I
got the following EurekaLog call stak information
|00507C4D|Servidor.exe|OverByteICSWSocket.pas|TCustomWSocket
|RaiseException
Éric,
Since ICS works asynchronous a reconnect-timer should be started from
event handler OnSessionClosed, is that the case?
Also the best place to destroy the object is from OnSessionClosed as
well.
But the OnSessionClosed event will be triggered if I try to connect to an
inacessible
Éric Fleming Bonilha wrote:
Éric,
Since ICS works asynchronous a reconnect-timer should be started from
event handler OnSessionClosed, is that the case?
Also the best place to destroy the object is from OnSessionClosed as
well.
But the OnSessionClosed event will be triggered if I try to
Hello Éric,
Actually I thing that this exception was raised because of the
architecture of my software and I need an opinion about that.
What is exacly the exception message ?
when I have some hosts down. My app has a Timeout parameter (Default 4
seconds) when if it doesn´t receives video
You have to call Abort once Connect has been called and OnSessionClosed
has not been triggered yet to abort the session. Then in OnSessionClosed
start the timer or post a custom message if you want to reconnect at once.
Ok, now I undestood, I will try to implement on that way
Thank you Arno!
Hello Wilfried,
What is exacly the exception message ?
The exception that was raised was Socket operation on non-socket (#10038 in
Disconnect (closesocket)).
and it was raised on this:
|00507C4D|Servidor.exe|OverByteICSWSocket.pas|TCustomWSocket
|RaiseException