🚀 go-pugleaf

Denis wrote:

> ... I was talking about one TClientSocket per process only to made
> the thinks simple.
> In the reality all process are server for all other process.

You are complicating things. Please do not speak about a process
as with c++builder one makes applications. You had already stated
that your application had one TServerSocket and one TClientSocket.
So it could act as a server and a client.

> The configuration is dynamic, but if I launch 3 process called A, B and C,
> the result of the connections are:
> 
> A ( server ) connect to B (client )
> A ( server ) connect to C(client )

Well already here I cannot follow you. A server does not connect
to a client. It is the other way round. Or did you mean 'is connected to' ?
A server can only listen and wait until a client makes a connection.
So the active player here is the client.

> B( server ) connect to A(client )
> B( server ) connect to C(client )
> 
> C( server ) connect to A(client )
> C( server ) connect to B (client )

In total this cannot be done with each application having only one
TServerSocket and one TClientsocket.

Cannot you rephrase the connections in this way:?

A ( TClientSocket ) connects to B (TServerSocket )
A ( TClientSocket ) connects to C (TServerSocket )

B ( TClientSocket ) connects to A (TServerSocket )
B ( TClientSocket ) connects to C (TServerSocket )

C ( TClientSocket ) connects to A (TServerSocket )
C ( TClientSocket ) connects to B (TServerSocket )

But for this each application needs two TClientSocket's.

> In this example A, B, and C have 1 TServerSocket and 3 TClientSocket.

3 ????

And where do you use the third for ? If you really use three than
give an example using TClientSocket1, TClientSocket2, TClientSocket3.

> So last question, how can I test if the connection is broken in the
> TClientSocket object ?
> Can I check the property Active ?

Probably. Or Socket->Connected.

But why do you want to check ? There are OnError and OnDisconnect
events which will tell you right away.

Hans.