🚀 go-pugleaf

Stefano Bonifazi wrote:

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

A TServerSocket can receive big files simultanuously from many clients.
Both in blocking and non-blocking mode.

A TServerSocket can send big files simultanuously to many clients.
Both in blocking and non-blocking mode.

All things need programming.

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

OnClientRead is triggered when the internal socket buffer is full
or when a certain time has elapsed. While your application reads
the data the socket can receive simultanuously.

>>>Why should I use the threaded way for a TClientSocket?
>>
>>Easier coding of the socket operations (your code does not have to be
>>separated amongst multiple event handlers), simultaneous processing of
>>multiple clients at a time, etc.
>>
> I always thought that one of the most important features of BCB vs VC was 
> the clearness due to the events handlers ...

With this advise I disagree. One can just use OnRead for a non-blocking
TClientSocket. There is only one eventhandler: OnRead who decides
what has to be done. And of course there are no multiple clients at a time
for a TClientSocket. Advising what to use is difficult as it depends
on what the clientapplication does besides sending and receiving.

Hans.