Humm, Markus wrote:
> The dll using that communication dll has one thread per socket
> (max. at most 10). Freing the socket is requested by this dll
> when it's execute method terminates.

And the socket has been _created in method execute as well?
How do you achieve that client sockets run in the client thread
if not using ThreadAttach/ThreadDetach? 


> So I don't think I need threadattach in the communication
> dll. Shared Mem is not used because so Strings are used. All params
> passed between these dlls are either numbers or pchars (which get copied
> to strings internally).
> So whare's the problem with my approach? Only TWSocket.close seems to
> hang. I will test a bit more now, maybe I find a solution but I don't know
> what causes the hang. But normally the sequence
> TWSocket.close;
> TWSocket.Free;
> is okay to terminate and release it?
> Greetings
> Markus
To unsubscribe or change your settings for TWSocket mailing list
please goto
Visit our website at

Reply via email to