🚀 go-pugleaf

"Okusmen" <okusmen@aselsan.com.tr> wrote in message
news:438ecb2f$1@newsgroups.borland.com...

>         try{
>                   SendSocket->Open();
>         }catch(const Exception &e){
>          CloseSendSocket();
>  }

That won't always work.  When Open() throws an exception, it can leave the
socket in an indeterminate state that Close() does not fully recover from.
You would be better off just freeing the TClientSocket object and then
reinstantiate it.  That ensures that all resources are fully released.

>       SendSocket->Close();
>       SendSocket->Port = 0;
>       SendSocket->Active = false;

Why are you closing the socket twice?

> void __fastcall TTCPSendDataModule::SendSocketError(TObject */*Sender*/,
>       TCustomWinSocket */*Socket*/, TErrorEvent /*ErrorEvent*/, int
&ErrorCode)
> {
>  try
>     {
>      ErrorCode = 0;
>     CloseSendSocket();
>  }catch(const Exception &e){
>  }
> }

You should be caling Close() on the Socket parameter, not the TClientSocket
object directly.


Gambit