Re: Indy Server -> client
- From: "Remy Lebeau \(TeamB\)" <no.spam@xxxxxxxxxxx>
- Date: Wed, 28 Feb 2007 13:59:02 -0800
"Thomas Mueller" <nospam@xxxxxxxxxxxx> wrote in message
news:45e5e716@xxxxxxxxxxxxxxxxxxxxxxxxx
I am trying to use the Indy components (version 10) in a way
that they apparently were not meant for:
Since you have not described what you are actually doing with them,
there is no way to know if you are using them correctly or not.
I have got a server app that can accept connections from multiple
clients. But in contrast to the normal way of the clients sending a
request and the server answering it, it want the server to keep the
connections and send requests to the clients to which they may or
may not answer.
That is perfectly fine to do, and Indy supports that model. There is
nothing in the TCP spec that says data has to flow from the client to
the server initially. TCP is bi-directional. Either party can write
to the socket at any time.
client ----connects to-------> server
client <---receives command--- server
client ----answers-----------> server
Simply write your command to the client in the server's OnConnect or
OnExecute event, and then read the reply back immediately.
I hope you get what I mean. Everything in Indy seems to be geared
toward making this impossible.
That is not true, not even close. What you are asking for is very
easy to do with Indy.
Gambit
.
- References:
- Indy Server -> client
- From: Thomas Mueller
- Indy Server -> client
- Prev by Date: Re: Advise on Thread code please
- Previous by thread: Re: Indy Server -> client
- Next by thread: Advise on Thread code please
- Index(es):
Relevant Pages
|
