Thanks Arno. Your opinion just validates our current understanding. The
only place in the entire RTL/VCL source tree where WSAAsyncSelect is called
is the old Socket Server project, which of course we are not using.
Tomorrow I'm going to take PortMon and Microsoft Network Monitor onsite and
see
At first you should find the source code that calls WSAAsyncSelect and
post the parameters passed here. However I doubt that Indy is calling
it since Indy uses blocking winsock API (WSAAsyncSelect makes the socket
non-blocking). At least a search in files for "WSAAsyncSelect" in the
XE2 source dire
I apologize up front for sending this message to the list. I'm hoping one
of the WinSock gurus here may have some thoughts on this strange issue. I
use ICS components in my own source code. However, this issue is NOT
related to the ICS components.
We have a DataSnap client talking to a DataSnap
