How do I safely shut down a thread, when I can't send a CEvent?
-
Hi, I'm working on making my own simple proxy server to learn a bit about socket programming. I'm also implementing the main loop as a seperate thread but since my CSocket.Accept(CSocket) call is in its own loop waiting for a connection, I can't send it a CEvent to shut down. Any help would be appreciated.
-
Hi, I'm working on making my own simple proxy server to learn a bit about socket programming. I'm also implementing the main loop as a seperate thread but since my CSocket.Accept(CSocket) call is in its own loop waiting for a connection, I can't send it a CEvent to shut down. Any help would be appreciated.
CSocket::CancelBlockingCall() will abort the Accept. --Mike-- ================== The original message was: Hi, I'm working on making my own simple proxy server to learn a bit about socket programming. I'm also implementing the main loop as a seperate thread but since my CSocket.Accept(CSocket) call is in its own loop waiting for a connection, I can't send it a CEvent to shut down.
Any help would be appreciated.
-
Hi, I'm working on making my own simple proxy server to learn a bit about socket programming. I'm also implementing the main loop as a seperate thread but since my CSocket.Accept(CSocket) call is in its own loop waiting for a connection, I can't send it a CEvent to shut down. Any help would be appreciated.
Accept in a loop? Thats not a correct way. Create a user interface thread of which the socket is a member and call Accept just once in the Initinstance of the thread ================== The original message was: Hi, I'm working on making my own simple proxy server to learn a bit about socket programming. I'm also implementing the main loop as a seperate thread but since my CSocket.Accept(CSocket) call is in its own loop waiting for a connection, I can't send it a CEvent to shut down.
Any help would be appreciated.