I am using TClientSocket now as I couldn't get on with TTCPClient either but am still getting the same thread closing issue. Seems like you are suggesting I look elsewhere for an equivalent which works - any suggestions?
JohnB -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Nelson Sent: 19 October 2006 17:25 To: Borland's Delphi Discussion List Subject: Re: Advice on Closing TtcpClient I haven't liked TtcpClient much, you are better off using TClientSocket directly. There might be 3rd party components out there that are better. But I found myself having to rewrite TTcpClient and TTcpServer for various reasons. ----- Original Message ----- From: "John Barrat" <[EMAIL PROTECTED]> To: "'Borland's Delphi Discussion List'" <[email protected]> Sent: Friday, September 29, 2006 4:52 AM Subject: Advice on Closing TtcpClient >I have built a control which embodies a TtcpClient control as a >sub-control. > In my test application for the control I have found that if I close the > application while the socket is still connected the application does not > close. The form dissappears but it remains as a running process in task > manager. > > What is the safe way of closing this process? > > I have tried things like While Socket.Connected do socket.close but that > doesn't seem to allow a clean shutdown. > > This is my first attempt at a control so applogies if the question is a > bit > naive. > > John Barrat > _______________________________________________ > Delphi mailing list -> [email protected] > http://www.elists.org/mailman/listinfo/delphi > _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
