🚀 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

Thank, looks perfect for what i needed. By the way 'Fetch' is it a BCB6
function or what?

Darl.


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:437cc79a$1@newsgroups.borland.com...
>
> "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
>
>
>

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

> Thank, looks perfect for what i needed. By the way
> 'Fetch' is it a BCB6 function or what?

It is an Indy function, in the IdGlobal unit.


Gambit

Thank again.
IdTCPClient or IdTCPServer doesn't have this property  "ReadTimeout" and how
do I change the default time as in
tcpclient->ReadLn(LF, IdTimeoutDefault); how do i make the server to LF as
line terminator and then change the default time value since ReadTimeout is
not a valid property.

Darl.

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:437cf568$1@newsgroups.borland.com...
>
> "Darlington ADIBE" <bcb@triative.com> wrote in message
> news:437cd28f@newsgroups.borland.com...
>
> > Thank, looks perfect for what i needed. By the way
> > 'Fetch' is it a BCB6 function or what?
>
> It is an Indy function, in the IdGlobal unit.
>
>
> Gambit
>
>

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

> IdTCPClient or IdTCPServer doesn't have this property
> "ReadTimeout"

Yes, they do.  It is a property of TIdTCPConnection in Indy 9 and of
TIdIOHandler in Indy 10.  If you don't have the property, then you must be
using the version of Indy that ships with BCB6.  That version of Indy is
VERY old and no longer supported.  You should seriously consider upgrading
to a newer version.


Gambit

> Yes, they do.  It is a property of TIdTCPConnection in Indy 9 and of
> TIdIOHandler in Indy 10.  If you don't have the property, then you must be
> using the version of Indy that ships with BCB6.  That version of Indy is
> VERY old and no longer supported.  You should seriously consider upgrading
> to a newer version.


I have up graded to indy9.

and now my server doesn't work again i get an access voilation error in the
Execute Event


void __fastcall TForm1::tcpExecute(TIdPeerThread *AThread)
{
  AnsiString cmd;
  AnsiString request;
  do{
    request = AThread->Connection->ReadLn(LF, -2);   <---- Error is thrown
here
    cmd = Fetch(request, "#");
    if(cmd == "AUTHEN") Authenticate(AThread, request);

  } while(cmd != AnsiString("DISCONT"));
  AThread->Connection->Disconnect();
}

I still don't see any property that allow me to change the default Line
Terminatior, that of ReadTimeout I saw

Darl.

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

> I have up graded to indy9.

Which build, though?

> and now my server doesn't work again i get an
> access voilation error in the Execute Event

Your code should not be looping at all.  The OnExecute event handler is
already looped internally by Indy.  Just process a single command and then
exit the handler, ie:

    void __fastcall TForm1::tcpExecute(TIdPeerThread *AThread)
    {
        AnsiString request = AThread->Connection->ReadLn(LF,
IdTimeoutDefault, -1);
        request.Delete(1, 1);
        AnsiString cmd = Fetch(request, "#");
        if( cmd == "AUTHEN" )
            Authenticate(AThread, request);
        else if( cmd == "DISCONT" )
            AThread->Connection->DisconnectSocket();
    }

You might also consider using the CommandHandler collection instead of the
OnExecute event.  The CommandHandler collection provides much automation
when it comes to parsing and processing textual commands.

> I still don't see any property that allow me to change the
> default Line Terminatior

There is no property for that.  Simply specify the desired line terminator
when calling ReadLn().  That is what its first parameter is for:

    AnsiString request =
AThread->Connection->ReadLn('YourLineDelimiterHere', IdTimeoutDefault, -1);


Gambit

Remy thank alot,

Indy 9.0.17 was very helpful, the CommandHandler made my code very easy and
well structured, though am still to figure how to use the some other new
features

I give it Up for the Indy Team.
I hope DevStudio2006  will support Indy 10 (as in C++ )

Darl.


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:437d3195$1@newsgroups.borland.com...
>
> "Darlington ADIBE" <bcb@triative.com> wrote in message
> news:437d20f2@newsgroups.borland.com...
>
> > I have up graded to indy9.
>
> Which build, though?
>
> > and now my server doesn't work again i get an
> > access voilation error in the Execute Event
>
> Your code should not be looping at all.  The OnExecute event handler is
> already looped internally by Indy.  Just process a single command and then
> exit the handler, ie:
>
>     void __fastcall TForm1::tcpExecute(TIdPeerThread *AThread)
>     {
>         AnsiString request = AThread->Connection->ReadLn(LF,
> IdTimeoutDefault, -1);
>         request.Delete(1, 1);
>         AnsiString cmd = Fetch(request, "#");
>         if( cmd == "AUTHEN" )
>             Authenticate(AThread, request);
>         else if( cmd == "DISCONT" )
>             AThread->Connection->DisconnectSocket();
>     }
>
> You might also consider using the CommandHandler collection instead of the
> OnExecute event.  The CommandHandler collection provides much automation
> when it comes to parsing and processing textual commands.
>
> > I still don't see any property that allow me to change the
> > default Line Terminatior
>
> There is no property for that.  Simply specify the desired line terminator
> when calling ReadLn().  That is what its first parameter is for:
>
>     AnsiString request =
> AThread->Connection->ReadLn('YourLineDelimiterHere',
IdTimeoutDefault, -1);
>
>
> Gambit
>
>

FYI:

I tried a move my core funtions into my COM Obj, which mean I had to now
manually include the nesesary header, since my COM have no Visual control.

I notict that when you #include <IdTCPClient.hpp>, i get error that alot of
variables was decleared early.
on examination i noticed that both the winsock2.h and winsock.h was include
along the IdTCPClient.hpp which is not the case if i had place the control
on the Form directly.

However i worked around it by #define _WINSOCKAPI_  just before #include
<IdTCPClient.hpp>

Am just wondering if I did some wrong along the line or if anybody have
noticed this too.

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

> I notict that when you #include <IdTCPClient.hpp>, i get error
> that alot of variables was decleared early. on examination i noticed
> that both the winsock2.h and winsock.h was include along the
> IdTCPClient.hpp

That is a known issue with Indy.  It is more of a Microsoft problem than an
Indy problem, though, because winsock.h and winsock2.h are not compatible
with each other.  The VCL uses winsock.h whereas Indy uses winsock2.h
instead.


Gambit