🚀 go-pugleaf

> A critical section should be locked for as short a time as
> possible, wrapping only the code that actually needs
> protecting.

Remy,

If the only job that my TServerSocket::OnGetThread
is to write a row (record) of data to some DB, can
that be considered fast (I expect up to 10 connections
at a time in the worst case)?

From my experience Insert()ing a row of data to a DB
is quite fast.

I ask that because of this:

You tought me how to receive data from server and send
some confirmation back directly from OnGetThread() to
client and that works fine for me.

But what if the operation in the OnGetThread() is not so
fast and I must have Critical Section because of accessing
the same files...

Do you think that I can because of fast escaping from
OnGetThread *only* store the *return* clients' addresses
and later use TClientSocket to send them confirmations
after processing?
Is that even possible because I have to pass the router?

To be more precise can I store ClientSocket in some list
and use it as a return address for confirmation?

void __fastcall TLanService::ServerSocketGetThread(TObject *Sender,
      TServerClientWinSocket *ClientSocket, < ---- STORE THIS
      TServerClientThread *&SocketThread)
{



-- 
Best regards,
Vladimir Stefanovic