🚀 go-pugleaf

Thanks very much for this, as always.

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:417eb3d1$1@newsgroups.borland.com...
>
> "Drew" <aemsley@brightwell.org.uk> wrote in message
> news:417eaff4@newsgroups.borland.com...
>
> > If the client does not disconnect cleanly, the TCP connection
> > remains established and does not appear to timeout.
>
> Yes, it will time out eventually.  It may take a long time, simply because
> the underlying socket stack itself (WinSock on Windows) can't detect
> abnormal disconnects in any timely fashion, but it will eventually time
out
> internally and decide the socket is no longer valid.
>
> > When the number of connections reaches the maximum allowed by the
> > TIdTCPServer (48), it quite rightly rejects all other attempts to
> reconnect.
>
> Correct.
>
> > 1.  What controls the TCP timeout period?
>
> The socket stack itself and its internal configurations.
>
> > 2.  What is the best way of the TCP Server detecting failed
> > connections in this way?
>
> Implement your own pinging type of system in your communications.  Have
your
> clients send a small packet to the server periodically (if not sending
> actual data for awhile) so that the server knows the connection is still
> alive.  If you do not receive any data after so much time, simply assume
the
> client is gone and close the connection yourself.
>
>
> Gambit
>
>