🚀 go-pugleaf

Denis wrote:

> I'm using many non-bloquing application with TServerSocket and
> TClientSocket.

Now which one is non-blocking ? Both ?

> There is many executable who are both client and servers. 

Please clarify:
There are more instances of your program. Each program has more than one
TServerSocket and more then one TClientSocket.

> At time 't' an application is server with 'n' client connected. In the same
> time this application is also a client connected to one or more servers.
> 
> My question: What exactly must i do when a client connection is broken ? 

Now which connection are you referring to ? A connection belonging to the
TServerSocket or to the TClientSocket?

> The
> socket is unusable and unable to reconnect to the server.
> So I must delete it and create a new client socket to lookup again the
> server.

So it was a clientconnection from you TClientSocket ? Of course
the TClientSocket can reconnect. Why not ?

> What is the right way, and the order, to process ??
> This a part of code that do actually this. ( this a client part ) is it
> correct ?
> 
> void __fastcall client::ServerError(TObject *Sender, TCustomWinSocket
> *Socket, TErrorEvent ErrorEvent, int &ErrorCode)

Please do not change the name of eventhandlers. I do not know about
'ServerError'. What exists though for TClientSocket is:

void __fastcall TForm1::ClientSocket1Error(TObject *Sender,
	  TCustomWinSocket *Socket, TErrorEvent ErrorEvent, int &ErrorCode)

> void __fastcall client::ServerDisconnect (TObject *Sender, TCustomWinSocket
> *Socket)

Do you mean for TClientSocket ?:
void __fastcall TForm1::ClientSocket1Disconnect(TObject *Sender,
		 TCustomWinSocket *Socket)

Think that it is not needed to delete the old and create a new
TClientSocket. But indeed you cannot reconnect in the same eventhandler.
Start a TTimer and reconnect in the TTimer eventhandler.

Hans.