Question

I have a server application with such structure:
There is one object, call him Server, that in endless cycle listens and accepts connections.
I have descendant class from CAsyncSocket, that has overriden event OnReceive, call him ProxySocket.
Also I have a thread pool with early created threads.

When connection is received by server object he accepts the new connection on the new object ProxySocket.
When data arrives to the ProxySocket, he creates a command object and gives it to thread pool. In this command object I giving the socket handle of a ProxySocket. When new object of command is creating – I creating a new Socket in working thread and attach handle to it.


My issue is next:
When command ends, socket doesn’t close, I just detach handle it and set CSocket handle to INVALID_SOCKET value, as planned. But my first ProxySocket object doesn’t receives messages of new data receiving after that. How can I solve this?

Answer 1

I don’t think you can use CAsyncSocket objects (or their descendants) in a thread pool secenario. CAsyncSockets are implemented on top of WSASsyncSelect – which tells the winsock to send notifcations to a window handle.
Because windows have thread affinity, one can never “move” the CAsyncSocket handling to a different thread.