CSocket and threads

[Beer]

hey all, say you have CSocket, or a plain WSA socket as a pointer member of a class, and you block the socket on a read method, and while it's blocked, you pass a reference to the class containing the socket to another thread through a casted pointer through the LPVOID pParam of a thread message, THEN, you start doing other operations on the CSocket from thread 2 through the pointer, while thread 1 has the thread on the blocked receive method. Like say thread 1 has the socket blocked receiving and thread 2 does a send on the same instance of the class with the m_pcsocket??? Does the world suddenly blow up if that happens? I used to do this all the time with java, but I'd like to know if it will properly work before I try it with CSocket. hey

[valikac]

No. I think given that a socket is blocked, you have to wait for the thread to free the socket. One solution is WSA non-blocking model. WSA modes will return immediately and allows any other threads to process the socket. Kuphryn

[Beer]

"void CancelBlockingCall( ); Remarks Call this member function to cancel a blocking call currently in progress." This is nuts, how are you going to cancel a blocking call if the call is blocked? They HAVE to mean from another thread right? Then you can cancel the receive before you send text then restart it right after your data is sent right? am i wrong or am i right? hey

[markkuk]

MFC CSockets can't be passed between threads. It should be possible with a plain WinSock socket.

[Beer]

It turned out I was actually looking for CSocket's OnReceive function, overriding that gave the class i was writing the desired effect. hey