🚀 go-pugleaf

qyte wrote:

> It could be just NULL, why do you stuck on such details. 

As you have problems with your code and asking us the reason
for them you might expect some questions. Now we do not
know if it is a detail or just the cause of. So then we ask.

You could prevent such question by better explaining what your
app should do and what the program flow is.

> I told That 
> this works but not when Both the client and the server send data at the 
> same time and wait then to receive the corresponding answer. 

I already told you also that we cannot comment on that before we
see how you handle the code around SendBuf() and ReceiveBuf().

 > There are
> not two instances. let's say that i am using it from my house and 
> connect with my friend 300 miles away. How is that not understood.

So there are two instances of your program indeed. One
instance acts as a server and the other as a client. Apparently
the user can choose if the app behaves like a client or a server.
It would have helped if you had told that rigth from the start.

> NOW do you know if i somehow can tell at a single moment if another 
> sock[t] t!=current, is sending or reiceving data? because i think the 
> mess is due to the winsock.

No the winsock is not te be blamed.

You are using both TServerSocket and all TClienSockets in non-blocking
mode ? (You could have told that before).

Winsicks can send all together (well threads on one CPU). But in
your application only one TClientSocket can send at the same time
and there is no sending and receiving at the same time.

Obviously there is something in your code that is not programmed well.

Thaks for trimming by the way. Go on trimming.

Hans.