🚀 go-pugleaf

Thanks for the response.

So a better way would perhaps be to store the OnExecute thread's thread id, 
and then send the OnExecute thread a 'thread message' (from my secondary 
thread) which it could pick up and send using AThread?

Would that avoid the problem?

And how many times can we use the word "thread" in a sentence? :-)

Thanks again,

- James


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:4172b877$1@newsgroups.borland.com...
>
> "James" <jb9@btinternet.com> wrote in message
> news:417256cf$1@newsgroups.borland.com...
>
>> Is AThread threadsafe?
>
> No.
>
>> Obviously there's a chance that the TCPServer's OnExecute
>> thread might try to send/receive data with the AThread, at the
>> same time as my other thread is using it to send data.
>>
>> Is this a problem?
>
> Yes.  Multiple threads cannot both read from the socket at the same time, 
> or
> both write to the socket at the same time.  They will step over each 
> other.
> You will have to provide some kind of synching to prevent that.
>
>
> Gambit
>
>