🚀 go-pugleaf

I am using Indy 10 that came with BDS2006, in C++.

My questions are about how to manage threads with the
Indy blocking sockets (previously I have only ever used
sockets in asynchronous mode with select()).

My application accepts multiple connections on a TIdTCPServer
and re-routes them all on the same TIdTCPClient connection,
then listens for responses and sends them back to where the
initial request came from.

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?

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.