🚀 go-pugleaf

"Old Wolf" <oldwolf@inspire.net.nz> wrote in message
news:466cbb16$1@newsgroups.borland.com...

> I have managed to write an OnExecute handler for the
> TIdTCPServer so that inbound packets can be read, and then
> call IdTCPClient1->Socket->Send to send it on upstream. Is
> IdTCPClient thread-safe or do I need some extra protection
> in here?

You need to serialize the writes yourself.

> I have been able to read responses by setting up a TTimer
> on the main form, and polling the IdTCPClient for incoming
> messages. However I'm not sure if this is the recommended
> strategy. Waiting for a blocking response in the same
> function where I sent the message to the IdTCPClient will
> not work because there I am in a thread of the Server, and
> the message received might be the message intended for a
> different thread.

I would suggest using two dedicated threads with the TIdTCPClient.
Have one thread contain a queue of outbound requests and continously
sends thems them when available, and another thread that continuously
reads the inbound responses that arrive.  That way, when your
TIdTCPServer receives a request, it can pass it on to the queue thread
and then continue on with its own things, and then the response thread
can pass the response back to the TIdTCPServer once it becomes
available.


Gambit