Thread: Implement TCP server in custom event

I need to add a TCP server to an existing code. The TCP server is started as a thread and it should raise an event to the parent as soon as a message is received in the socket from a client. The parent should stop the TCP thread, treat the message and restart the TCP server with a back message to be sent via the socket to the client.
There are several issues here; I know how to create the TCP server and to create a thread. I would like to have some guidance on how to put all together so that to implement a custom event when the TCP input buffer is full.
Thanks

You are right regarding the architecture complexity. But there are several reasons for taking out message processing from the TCP server (one is multi-user).
Now, to structure my need:
- I have a main that creates and starts a thread and an event
- The thread runs a TCP-server-function in a listen loop. It doesn't block the main thread.
- The event is fired when the TCP-server-function gets an input message in the socket buffer.
- The event executes a "callback" function in the main thread.
I ahev worked in C++, Java, C# with such built-in patterns but I haven't tried in C so far.
I am in a Windows environment.
If you have some link to a simple working example I'd appreciate.

In fact this is my top description case:
I have a main program in C that does machine learning in an infinite loop, just printing out from time to time, at the console, about different processing phases ans steps.
This program processes data from a huge volume of files and gets, when needed, on-going parameters entered from console. I interrupt the infinite loop the get these parameters by using the Windows _kbhit() function. Hitting the keyboard stops the infinite loop and I can implement whatever I want through a function that eventually relaunch the infinite loop. It works as an event(hitting the key) + callback (the function).
Now, the main program must evolve to have parameters provided also from an external application, that can communicate via TCP sockets. Therefore, I want to replicate the "_kbhit() + function" model, as described, into a TCP server + call back. I can put the TCP server into a thread, but as soon as it gets data from the external application it has to raise an event that stops the main program infinite loop. So this is my problem. In fact all is summarized to implement concurrent asynchrounous processes in C. More precisely, to create an event triggered in the TCP server thread, then to execute the function that will stop the infinite loop etc. as described.
My concern now is how to create the event and fire it when the TCP server gets data from socket. I don't think WaitForSingleObject is appropriate (puts the parent process on wait, so the infinite loop is stopped), or I don't know how to use it.

Thanks Salem for your assistance.
I have solved the problem, which, in fact, was about event + callback. I just used signal(SIGINT, callback) in main, and raise(SIGINT) in the thread.
Now about select(), it's true that is also handy but as I had to: listen-to-socket/get-data/process-data/send-back-data-to-socket I've kept the TCP server for full communication protocol with the external application (a Node JS one).
Veeeery easy in fact, just had to know :-)!