🚀 go-pugleaf

Thanks for Your infinite patience Mr Lebeau!

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> ha scritto nel messaggio 
news:41ffd045$1@newsgroups.borland.com...
>
> Well, there is a caveat to the OnWrite events - if you make a blocking 
> call
> on a non-blocking socket,

Which for instance?

>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.

May I use Application->ProcessMessages() instead?

>> 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).

My server has to support many clients (not more than a hundred though!), and 
it's application have only to store what it receive or at least re-send that

>> 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.
>
As You said in the other message that thread code only have to receive / 
send the data, so it does not matter if it has to wait ... the program main 
thread is free to do whatever meanwhile!:)

Thanks Gambit!!!!!!!!!!!!!!!!!!!!!!!!!!!!!