🚀 go-pugleaf

"Lesley Anne" <mspfila-ng@yahoo.com> wrote in message
news:44f5c67a$1@newsgroups.borland.com...

> So, if the disconnect will be coming from the client's end of the
> connection, is the best way to make sure the component recognizes
> that disconect to periodically try to read from all connections,
> trusting that they'll error out correctly when the connection is no
> longer active?

It is the only way to do it.  Indy uses blocking sockets, and such sockets
must be read from, or written to, in order to detect a graceful disconnect
from the other party.

> I thought at first that would be simple enough to do, but I'm having
> a hard time finding how to even access all the (apparent) connections.

Why just just read inside the server's OnExecute event?  It is triggered on
a per-connection basis.

If you must access the connections via a list, then you can reach them
through the server's Threads (Indy 9) or Contexts (Indy 10) property.

> The best I could come up with to even see how many connections I
> have is Server1->Bindings->Items->Collection->Count

That is not correct.  The Bindings collection contains the listening sockets
that the server uses to accept incoming connections.  The actual connections
are kept tracked of separately.

> How would you normally tell an application to do something with
> each connection on a TIdTCPServer?

You should be doing everything in the OnExecute event.  But, if you must
access one or more connections outside of that, then you must go through the
server's Threads/Contexts property. By aware that TIdTCPServer is
multi-threaded, so make sure your reading/writing is thread-safe.


Gambit