🚀 go-pugleaf

Hi All,

Am doing an App using the indy TCP server/Client componnet and i need an
adivce on how best to handle the situation am about the describle below.

the tcp client is in a COM object with the following methods Authenticat,
Send, etc....,
when the host  client app (exe using my COM API) calls the authenticate
method, my com obj tries to connect to a TCP Server on a remote machine, if
connected it send the uid and pwd parameter pass through authenticate to the
server msg format "#AUTHEN#xxxx#xxxx# where AUTHEN = do Authentication,
first xxxx = Username, second xxxx = password, the server check the
username/password pairs in a database, if correct it sends back #AUTHEN#OK#
if not it sends #AUTHEN#ERR#xxxxxxx# where xxxxx = reason of then Error.

The situation above i have don so far, the issue is in the client end, when
the exe call the com api Authenticate(uid, pwd), I don't want the method
(authenticate) to return untill the server send back #AUTHEN#OK# or
#AUTHEN#ERR#xxxxxx# or a RTimeout property of the COM obj is reached
RTimeout is the Rececive Time Out propety of the con obj that indicate how
long to wait before expected receive times out.

Any profession advice on how to implement this "wait for reply" issue


Darl.