🚀 go-pugleaf

"Lapo Guidi" <lapoguidi@inwind.it> wrote in message
news:457f3780$1@newsgroups.borland.com...

> when the Client send a command with SendCmd, function doesn't return
> untill Reply and Response; the receiving thread I coded will steal the
Reply
> and the Response that SendCmd is waiting for?

Yes, it can (and vice versa, SendCmd() can steal data that the thread may be
waiting on).  Which is why you can't use SendCmd() anymore if you are using
a reading thread.  You will have to use WriteLn() instead, and then do all
of your reply processing inside of the thread as well.  So you are going to
have to design your data protocol in such as way that the thread will be
able to tell which packets are command replies and which ones are not.

One way around that is to wrap the connection in a critical section.  Then
you can "lock" the connection before calling SendCmd() and "unlock" it
afterwards.  Then the thread will not be able to read from the socket while
it is busy waiting for a command reply.

Othrwise, you will just have to go back to using a Timer again and forget
the thread altogether.


Gambit