🚀 go-pugleaf

Bob,

Thanks again for answering. I have tried to calrify a little better below.


"Bob Gonder" <notbg@notmindspring.invalid> wrote in message 
news:f67p21pil8brk4cg777ivcm87aresmjbe1@4ax.com...
> mike wrote:
>
>>> You weren't clear if the "Clients" are just several threads in a
>>> single Process, or seperate Processes.
>>
>>The Clients connect to a single process and each connection is a thread
>>within the process.
>
> Still not clear. Are you saying there are several Client processes
> connecting to a single Server process that is multi-threaded?
>
> And, is it the Clients that use the DLL or the Server?
>

The Clients connect to the server process, and the Server Process is 
multi-threaded and it is the Server that uses the DLL not the Clients.



> If the DLL hangs on to the data, or is "statefull" (remembers what it
> is doing), then all threads will see the same state/data, and you will
> likely have problems using it multi-threaded.
>

The DLL does not hold on to any data. It simply processes a request and 
sends the data back to the calling process.

>
> If the DLL hands you the data, and then doesn't remember it, then yes,
> you can save the data in your thread (local stack variable). And, if
> the code isn't reentrant, then I suppose some locking mechanism is in
> order.

So would I use the syncronize method from the thread to the call to the DLL 
and then save any necessary data in the thread local stack.

Thanks for the continued information.

Mike