Quote Originally Posted by wysota View Post
You have to post a request to an object living in the thread handling the socket and then handle that request in the proper thread.
I assure this by signaling to the proper thread. this is working right...

Quote Originally Posted by wysota View Post
However you really don't need any extra threads here. You can take the code above, strip it of all mutexes, run it in the gui thread and it will work just fine and faster than if you used threads.
So i am not getting any benefits from using threads here, but the amount of information being handle is very big. there is new values coming from serial ports (5) around 10 values/sec from each port that have to "deserialize", analyze and do specific actions.
The gui displays this information assign it to specific widget and has to send it to the clients, when there is many clients connected, will the gui have a latency?