Hello Dod,
I think you have to override the Notification method of
TWSocketServer. I only did a quick look..
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
Sunday, March 19, 2006, 22:28, Dod wrote:
> Hello Wilfried,
> Yes, I came
Hello Wilfried,
Yes, I came to same conclusion too when you told me it worked fine
with TWSocket. Now I simply set FSessionClosedFlag:=False before
calling .Connect again and all is fine. I also added some
FConnectDidError:=ErrCode in OnSessionConnected sowhe
Hi Dod,
Did some additional research. If you wants to use TWSocketClient instead
of TWSocket to initiate a connection, then you have to set
FSessionClosedFlag := False; in the OnSessionClosed event. If you do not
then OnSessionClosed will not trigger a second time.
---
Rgds, Wilfried [TeamICS]
ht
Hello Dod,
> In the SessionClosed I start a Timer that will send a message 20
> second later to retry a .Connect, but this new try will only produce a
> OnSessionConnected not followed by a SessionClosed, any idea why ?
I examined the project that demonstrate the problem. The client you use
Hello Dod,
> In the SessionClosed I start a Timer that will send a message 20
> second later to retry a .Connect,
This is the correct way to do it.
> but this new try will only produce a
> OnSessionConnected not followed by a SessionClosed
Never had that situation. In al my automated prog
Hello,
I am actually doing some crash test on my server to handle as many
situations as possible.
I have a problem in a failed socket .Connect
I create a few sockets to .Connect them to some remote points. The
.Connect will excecute and fail because there is nothing listening on
destina
