🚀 go-pugleaf

Hi,

I am using C++ Builder 2006 with indy 9 (9.0.50?) components.

I believe the "Keep Alive" code I have implemented in negatively
affecting the TIdTCPClients ability to reconnect to the
TidTCPServer. When a client reconnects prior to the server 
realizing that the connection was severed, the client 
disconnects immediately after reconnecting.

I believe (guess) that the Keep Alive code is in the process of
 failing as the client is reconnecting. If I remove the Keep 
Alive code, reconnections always succeeds. If I wait until the 
server realizes that the connections have severed, reconnections
always succeed.



I have the following code in a TimerEvent ( every 10 seconds) 
as my implementation of "Keep Alive" code between clients 
(TidTCPClient) and server

//code to ping\keep alive to all connected clients

TList *list = IdTCPServer->Threads->LockList();

try
{
  for( int i = 0 ; i < list->Count ; i++)
  {
    TIdPeerThread *thread = static_cast<TIdPeerThread*>(list->Items[i]);
   
    if (thread->Connection->Socket->Connected())
    {
       strResponse = SendMessageToClient(thread,strPING,8000 /* timeout value*/);
    }
    else
    {
		
       //return faillure
    }
  }

}
catch(...)
{
   IdTCPServer->Threads->UnlockList();
}

   
IdTCPServer->Threads->UnlockList();

//----------------------------------------------
The rest of my implementation is similar to this 

http://tinyurl.com/2bq4vt

Any ideas or suggestions on how to prevent the keep alive code
from affecting cient reconnections will be greatly appreciated.

Regards,

JohnG