> I already modified the client in a way that it explicitely polls Windows
> messages for 50 sec. even, but that doesn't help.
A valid message pump is essential for TWSocket to work. When you build a
DLL, you depends on the host application except if you put all socket stuff
in a worked thread w
Hello,
I'm using V5's TWSocket in D2007 and have a strange problem which
doesn't always occur but approx. 2-3 times out of 10 tries.
I have two applications running on the same PC "connected" via a
TWSocket TCP connection (127.0.0.1). The client side is in a COM
automation DLL (I think single th
