🚀 go-pugleaf

Hans Galema wrote:
> qyte wrote:
> 
> Please do not quote a whole reply. Just some lines will do.
> 
>> Let's say that i have four TClientSockets And 1 TServerSocket;
> 
> 
> In one application ? Or one server application and four client
> applications ?
> 
>  > During
> 
>> their OnConnect events i have declared the following:
>> TCustomWinSocket *sock[4];
> 
> 
> Are you doing that both for a TClientSocket AND a TServerSocket ?
> If so, why ?
> 
>> In The Server sock[ActiveConnections-1]=Socket;
> 
> 
> Please tell when you execute that statement. ActiveConnections
> often does not contain the right amount immediately.
> 
>> and in each client i assosciate them like sock[0]=Socket...
> 
> 
> I do not understand why a client has to bother with other
> clients.
> 
>> Because I Know the order in which they connect.
> 
> 
> Even if you know that. Never trust the Connections[] array
> for keeping that sequence.
> 
>> how can i be certain that when i call sock[0]->SendBuf No other can 
>> read(mainly) or write at the same time. It is abvious that they are 
>> all using the same port. 
> 
> 
> Please explain first what should happen. It looks as if you
> have a TServerSocket and upon connection of a client you use
> a TClientSocket to communicate with that client ?
> 
> That would be a strange construction.
> 
> Hans.



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. 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]);
}

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.