🚀 go-pugleaf

"Vin�cius" <vgalo2000@yahoo.com.br> wrote in message
news:41f91ff2@newsgroups.borland.com...

> There is a IdTCPClient1->ReadBuffer(...), but I can't call this
> in some structure like execute on the server or an event that set
> when the buffer has something to read for the client.

Yes, you can.  You just have to set it up yourself first.  See my other
reply.

> I take a look at "onWork" event but I don't understand how to use it.

OnWork has nothing to do with what you are asking for.

> In TClientSocket there is an event "OnClientRead", where
> we can read buffers when its something to read.

Indy is not an event-driven library to begin with.  When you want data, you
simply read the socket, and the reading does not return until data actually
arrives.  If you do not know when data will arrive, then you have to move
the reading into its own thread so that the reading will block the thread
and not the rest of your code.  The alternative is to use a timer instead,
calling ReadFromStack() periodically with a small timeout, and then process
any available data when the InputBuffer->Size is greater than zero.

> This also exists, "AThread->Connection->WriteBuffer()", but only
> can be called inside the events of the server, or I wrong??

You are wrong.  You can call WriteBuffer() at any time from anywhere you
want.  All you need is a pointer to the Connection.  From outside the event
handlers, you can use the server's ActiveThreads property to gain access to
the Connections that are currently running.

> there no exists IdTCPServer->WriteBuffer()

TIdTCPServer hosts multiple connections.  You need to call WriteBuffer() on
the particular connection that you are actually interested in writing to.


Gambit