🚀 go-pugleaf

"Michele Santucci" <michele.santucci.nospam@nospam.celinavio.it> wrote in
message news:40e2baf1@newsgroups.borland.com...

> I need to write a server that's capable of accepting
> just one connection

Use TIdSimpleServer instead of TIdTCPServer.  TIdSimpleServer is a
simplified TIdTCPServer specifically designed to handle a single connection
at a time.

> My first doubt is about the OnExchange event ..

There is no OnExchange event in Indy.  Perhaps you mean OnExecute?

> is it triggered just when the server spawn for the first time
> the peer thread or each time something happens to the peer
> connection (read data, write data, disconnection)?

Assuming you do mean OnExecute, then it is triggered in a loop for the
lifetime of the connection regardless of what is actually happening on the
socket.  It is the inner body of a "while not Terminated" loop for
TThread.Execute(), ie:

    procedure TIdThread.Execute;
    begin
        //...
        while not Terminated do begin
            //...
            BeforeRun;
            while not Stopped do Run;
            AfterRun;
        end;
        //...
    end;

    procedure TIdPeerThread.Run;
    begin
        //...
        // triggers the TIdTCPServer.OnExecute event
        Connection.Server.DoExecute(Self)
        //...
    end;

> Then.. what's the best way to handle safely peer's
> disconnections and server shutdowns?

All of that is already handled for you, as long as you are not doing your
own exception handling in the OnExecute event handler that prevents Indy
exceptions from reaching back to the TIdTCPServer for its own processing.

> I tried in several ways but I always have errors of all kinds.

Please be more specific.


Gambit