Newsgroups : Borland : borland.public.delphi.internet.winsock : 2007 Sep : Re: TTcpServer
| Subject: | Re: TTcpServer |
| Posted by: | "Remy Lebeau (TeamB)" (no.spam@no.spam.com) |
| Date: | Tue, 18 Sep 2007 15:27:35 |
"Tristan Leask" <no@no.com> wrote in message
news:46f03908$1@newsgroups.borland.com...
> Now if i drop one of these onto my form, then the code
> then moans about TTcpServer being an undeclared identifier.
Sounds like you don't have the "Sockets" unit in your uses clause.
With that said, TTcpClient and TTcpServer are not very well-designed
components to begin with. They were Borland's attempt at cross-platform
sockets when they first started supporting Linux in D6. But they are not
implemented very well, requiring a lot of manual work on the programmer's
part. You would be much better off sticking with the old TClientSocket and
TServerSocket components (install the dclSockets100 package if it is
available) or use third-party components, such a Indy (which ships with
BDS), ICS, Synapse, etc.
Gambit