🚀 go-pugleaf

"Darlington ADIBE" <bcb@triative.com> wrote in message
news:437c328b@newsgroups.borland.com...

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

Indy already implements all of that for you.  Simply read from the socket
immediately after you write to it.  The reading will not return until data
is actually received, or a timeout/error occurs.  For example:

    HRESULT __stdcall TMyComObjImpl::Authenticate(BSTR uid, BSTR pwd)
    {
        try
        {
            AnsiString Cmd;
            AnsiString Response;
            AnsiString Status;

            Cmd.sprintf("#AUTHEN#%s#%s#", AnsiString(uid).c_str(),
AnsiString(pwd).c_str());

            TCPClient->Connect(5000);
            try
            {
                TCPClient->WriteLn(Cmd);
                Response = TCPClient->ReadLn(LF, IdTimeoutDefault; -1);

                Response.Delete(1,1);
                if( Fetch(Response, "#") != "AUTHEN" )
                    throw Exception("Unknown response");

                Status = Fetch(Response, "#");
                if( Status != "OK" )
                {
                    if( Status == "ERR" )
                        throw Exception("Authentication failed: " +
Fetch(Response, "#"));
                    else
                        throw Exception("Unknown response");
                }
            }
            catch(const Exception &)
            {
                TCPClient->Disconnect();
                throw;
            }
        }
        catch(const Exception &e)
        {
            return Error(e.Message, IID_IMyComObj);
        }
        return S_OK;
    }

    HRESULT __stdcall TMyComObjImpl::get_RTimeout(long *Result)
    {
        *Result = TCPClient->ReadTimeout;
        return S_OK;
    }

    HRESULT __stdcall TMyComObjImpl::set_RTimeout(long Value)
    {
        TCPClient->ReadTimeout = Value;
        return S_OK;
    }


Gambit