I am writing a regular DLL (using shared MFC) that works with CSockets.
This DLL is loaded by a service that has no message pump.
I created a UI thread (derived from CWinThread) and all socket-related
work is done from here. I can connect to the server, send messages,
etc. The problem is that OnReceive is never called on my socket.
Does anyone have an idea what might be the problem?
Re: CSocket, DLL and OnReceive never being called ... I am writing a regular DLL that works with CSockets. ... The problem is that OnReceive is never called on my socket.... but CSocket would not ever call OnReceive since CSocket is ... Make sure that your code returns to the CWinThread message pump.... (microsoft.public.vc.mfc)
Re: CSocket, DLL and OnReceive never being called ... I am writing a regular DLL that works with CSockets. ... This DLL is loaded by a service that has no message pump.... The problem is that OnReceive is never called on my socket.... but CSocket would not ever call OnReceive since CSocket is ... (microsoft.public.vc.mfc)
Re: How to make a CSocket console app using VC6 appwizard ... >> It's my understanding that CSocket needs a message pump only if the ... It's true that CSocket is inherently an asynchronous socket, ...int CSocket::Receive ... (microsoft.public.vc.mfc)
Re: UI Thread and CSocket ... The message pump definitely does not run when a UI thread is ... > MFC multithread socket example code? ... This is an CSocket object,... Within that CWinThread object, there is an instance of the CSocket. ... (microsoft.public.vc.mfc)
Re: CAsyncSocket OnReceive() never called ... The thread in which the socket is created must be a message-driven ... A worker thread does not dispatch ... After I connect the socket and send a request to the server, ... The thread must have a message pump,... (microsoft.public.vc.mfc)
