🚀 go-pugleaf

> I have implemented asynchronous protocols using server threads.  They work
> fine.

Is that using blocking or unblocking modes?

>> as depending how long you are prepared to wait can delay transmitting
> data.
>
> Not necessarily.
>

If using blocking mode and spawning threads, what is a reasonable "wait for 
data" time to avoid a delay in trasmitting? 10ms?
I have heard from other engineers (not using BCB), that they have written 
async protocols by having a socket for Rx and a socket for Tx.  Have you 
used such an approach?  Any drawbacks or advantages?

> They do, if you use them in non-blocking mode.  Then you don't need 
> threads.
> But then you can only process data as fast as you can process queued
> messages.

Just to confirm, if using non-blocking and no threads, the "on socket read" 
and "on socket write" events are async?

Last two questions (sorry to be annoying):

1)  Is it ok to instantiate the server and client components in a thread, if 
so, can it be done like this:
        Ssocket = new TServerSocket(NULL);

2)  Is there a property to restrict the number of clients the server 
component can accept, if not, whats the sequence the server events should go 
through to reject the connection?

Thanks

Paul.