| View previous topic :: View next topic |
| Author |
Message |
Ugo Galbiati
Guest
|
 Posted: Mon Nov 03, 2003 5:33 pm Post subject: Tcp client/server at design time |
 |
|
Hi,
does anyone know any component for tcp/winsock that work at design time?
Thanks,
Ugo Galbiati.
|
|
| Back to top |
|
 |
Yahia El-Qasem
Guest
|
| Posted: Mon Nov 03, 2003 5:40 pm Post subject: Re: Tcp client/server at design time |
|
|
what should it do at design time ?
Yahia
|
|
| Back to top |
|
|
Ugo Galbiati
Guest
|
| Posted: Tue Nov 04, 2003 8:16 am Post subject: Re: Tcp client/server at design time |
|
|
| Quote: | what should it do at design time ?
Yahia
|
My goal is to develop two components that communicate something eachother;
at runtime they could be located in different computers. I started using
Indy components but I discovered that they can work just at runtime, like
all the socket components that I've found on internet.
What I need is a tcp server component multi-thread, and a tcp client
component able to connect to the server and send/receive bytes.
Ugo Galbiati.
|
|
| Back to top |
|
|
John Smith
Guest
|
| Posted: Wed Dec 10, 2003 6:49 am Post subject: Re: Tcp client/server at design time |
|
|
use TIdTCPServer and TIdTCPClient.TIdTCPServer is multi-thread.
"Ugo Galbiati" <ugo.galbiati (AT) ebus (DOT) it> дÈëÓʼþ
news:3fa75fc5$1 (AT) newsgroups (DOT) borland.com...
| Quote: | what should it do at design time ?
Yahia
My goal is to develop two components that communicate something eachother;
at runtime they could be located in different computers. I started using
Indy components but I discovered that they can work just at runtime, like
all the socket components that I've found on internet.
What I need is a tcp server component multi-thread, and a tcp client
component able to connect to the server and send/receive bytes.
Ugo Galbiati.
|
|
|
| Back to top |
|
|
Chris Mantoulidis
Guest
|
| Posted: Thu Dec 11, 2003 6:19 pm Post subject: Re: Tcp client/server at design time |
|
|
"John Smith" <thecoder (AT) 163 (DOT) com> wrote
| Quote: | use TIdTCPServer and TIdTCPClient.TIdTCPServer is multi-thread.
"Ugo Galbiati" <ugo.galbiati (AT) ebus (DOT) it> дÈëÓʼþ
news:3fa75fc5$1 (AT) newsgroups (DOT) borland.com...
what should it do at design time ?
Yahia
My goal is to develop two components that communicate something eachother;
at runtime they could be located in different computers. I started using
Indy components but I discovered that they can work just at runtime, like
all the socket components that I've found on internet.
What I need is a tcp server component multi-thread, and a tcp client
component able to connect to the server and send/receive bytes.
Ugo Galbiati.
|
Why the heck would you need them to communicate on design time?? Your
problem doesn't seem to need them to communicate on design time.
|
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
