🚀 go-pugleaf

qyte wrote:
> Hans Galema wrote:

>> Please do not quote a whole reply. Just some lines will do.

Please trim!. It is also very annoying that we have to scroll down
so much to read your reply.

> on the server on connect i send back an int to start the connection of 
> the second client and so on. This works perfectly good.

So a TServerClientSocket connects. And upon connection waits to
receive an int and if it has done so it would activate another
TClientSocket connectiong to the same server ? And so on ?

> I have no 
> problem with the assignments. the server socket read functions is the 
> following and that works good as well. don't doubt about that.
> 
> {
>         if(Socket==sock[0])
>                 ClientSocketRead(ServerSocket,sock[0]);
>         if(Socket==sock[1])
>                 ClientSocket_s2Read(ServerSocket,sock[1]);
>         if(Socket==sock[2])
>                 ClientSocket_s1Read(ServerSocket,sock[2]);
>         if(Socket==sock[3])
>                 ClientSocket_mRead(ServerSocket,sock[3]);

         if(Socket==sock[0])
                 ClientSocketRead(ServerSocket,Socket);
         if(Socket==sock[1])
                 ClientSocket_s2Read(ServerSocket,Socket);
         if(Socket==sock[2])
                 ClientSocket_s1Read(ServerSocket,Socket);
         if(Socket==sock[3])
                 ClientSocket_mRead(ServerSocket,Socket);

Why do all these functions need the ServerSocket as parameter ?

> just sometimes when i send data from both sides and responce is expected 
> then there is confusion and they both stop transmiting. I don't know how 
> could this be since sock[1] sends and sock[2] receives. when sock[1] 
> receives above it considers only specific actions such as abort etc. 
> That happens extremely Rarely.

To comment on that we need to know more about your code. Especially
your errorchecking around SendBuf() and ReceiveBuf().

Repeat: Please do not send back all this text if you reply.

Hans.