I am trying to use CAsyncSocket to create two separate sockets in two separate threads. One is being created in the main application thread, the other in a worker thread. I have no problems creating the socket in the main thread, but when I try to call Create() in the worker thread, the call dies inside CAsyncSocket. I traced through the MFC code and it seems there are some thread local data structures which store the socket handles used by CAsyncSocket. These structures appear not to have been intialized for my worker thread as the pointers to them are NULL. After some further searching I found that these data structures are initialized by AfxSocketInit(). I found that if I call AfxSocketInit() from within my worker thread, I can create sockets within it. This only workes if I remove the AfxSocketInit() from my main thread as MFC doesn't let you Initialize sockets twice. This prevents me from being able to create sockets in the main thread.
I find it hard to believe that there is no way to create CAsyncSockets in multiple threads and I have seen nothing in the documentation that would indicate that this is the case. Therefore I assume I must be doing something wrong. Is there anything I need to do to prepare a thread to create a socket? Would it help if I used a user interface thread instead of a worker thread? Is there some sort of limitation on using CAsyncSocket with multiple threads? Any help would be appreciated....
In order to achieve ansynchronous operation of socket, MFC will create a window for a socket as a sink object to receive Socket Messages. So that in order to use Socket class of MFC, you must have a message loop for the thread which the Socket Class is created in.
To resolve the problem you have 2 choice:
1)Add a message loop to your work thread.
2)Use the socket API directly.( I preferred to this one. For CAnsyncSocket is designed to use in a single thread especially.)
0
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.
One of a set of tools we're offering as a way of saying thank you for being a part of the community.
In order to achieve ansynchronous operation of socket, MFC will create a window for a socket as a sink object to receive Socket Messages. So that in order to use Socket class of MFC, you must have a message loop for the thread which the Socket Class is created in.
To resolve the problem you have 2 choice:
1)Add a message loop to your work thread.
2)Use the socket API directly.( I preferred to this one. For CAnsyncSocket is designed to use in a single thread especially.)