🚀 go-pugleaf

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:41ffd228$1@newsgroups.borland.com...
>

Thanks Remy once more time! :-)

>> - with non-blocking the server socket can receive simultaneously
>> from many clients
>
> The server can do that regardless of blocking or non-blocking.
>

Good!

> Yes.  However, the data in the socket is already buffered in memory by the
> time the OnClientRead event is triggered.  You can query how many data is
> actually available via ReceiveLength() and then perform a single read to
> copy the entire buffer into your application's own buffers in a single
> operation very quickly.  If your processing of the data is simple, the 
> event
> handler will exit relatively quickly, and other sockets can then be 
> serviced
> just as quickly.  If, on the other hand, your processing of the data can 
> be
> time-consuming, then you should copy the data to a different thread so 
> that
> the event handler can exit as soon as possible.

Great! That's music for my ears!

> A thread that is reading from a blocking socket doesn't need to do 
> anything
> else while it is reading, so blocking the thread is fine.

Fine! So I guess that in non blocking mode Borland or Microsoft have their 
"threads" setting " while receiving from the different clients!

>> I should be able to have a non-blocking Client and a ThreadBlocking 
>> server
>
> Correct.
>
GOOOD New!!

>> The problem is that with the simple test I'm posting in this thread right
>> now the Threadblocking server does nothing with my simple non-blocking
>> client...
>
> You are probably not using it correctly.

OK but the main problem is that even if I searched all google as You 
suggested I only could find examples of Threadblocking ServerSocket using 
the user made Threads with TWinSocketStream, nothing using the common 
OnClientRead event! :(

Thanks again Gambit! Have You never thought to take a University seat? I 
would pay gold to have such a teacher!:)