🚀 go-pugleaf

"Simon Guertin" <sguertin_AT@trellianetworks.com> wrote in message
news:427a6397@newsgroups.borland.com...

> I would have like to have all my processing code in another class.

Then do so.  There is nothing preventing you from doing that.

> This class will takeover the client communication since it is
> not really the best place to take care of that in the event of
> TIdTCPServer OnExecute Event.

Why not?  Please elaborate.

> By processing everything in the OnExecute Method, it will not
> be good programming practice I beleive. I think the way the
> Java class handles the client connexion is a good way of OO
> programming.

Your Java code is not doing anything that cannot be done in Indy as well.
For example:

    procedure TForm1.IdTCPServer1Connect(AThread: TIdPeerThread);
    begin
        AThread.Connection.WriteLn('whatever your greeting is');
    end;

    procedure TForm1.IdTCPServer1Execute(AThread: TIdPeerThread);
    var
        inputLine, outputLine: String ;
    begin
        inputLine = AThread.Connection.ReadLn;
        //...
        AThread.Connection.WriteLn('whatever your response is');
        if (should disconnect) then AThread.Connection.DisconnectSocket;
    end;


Gambit