🚀 go-pugleaf

"Stefano Bonifazi" <stefboombastic@email.it> wrote in message
news:41ff64b9@newsgroups.borland.com...

> Great!! Thanks!! Now finally I understand what that event is needed for!:)

Well, there is a caveat to the OnWrite events - if you make a blocking call
on a non-blocking socket, the call will fail with a WSAEWOULDBLOCK error
code, and you have to wait until the OnWrite event is triggered before you
can send more data to the socket again.

> My needs are that the server can send or receive those big files
> at the same time without one client sitting while waiting for others!

That is not what I meant.  I was referring to the requirements of the server
(how many clients it should service, what kind of application you are using
the code in, etc).

> Sorry but I still don't understand :( What do You mean with calling code?

The code that is calling SendBuf(), ReceiveBuf(), etc.  In other words, the
code that is sending/reading the data to/from the socket.

> that is the OnClientRead is triggered once the socket has finished
> to receive, Do I mistake?

OnClientRead is triggered when data has arrived on the socket but has not
been read by the application yet..

> I always thought that one of the most important features of BCB
> vs VC was the clearness due to the events handlers ...

Setting up event handlers in general is clean.  Actually using events to
control your processing can break up your code logic and make it difficult
to manage and/or debug.


Gambit