QWebSocketServer howto move new connections to a own thread

[wysota]

Why?

Because usually the number of threads you can spawn per process or per user is limited. By opening a large number of concurrent connections I'd either force your app to run out of threads or starve it by flooding it with context switching.

Why threads? -> Maybe every connection can do a blocking operation in my application and therefore I want to decouple them from the rest of the application/listener.

Then you want to perform that blocking operation in another thread (or better yet using a limited thread pool) and not push the whole communication there. You can decouple whatever you want decoupled by encapsulating it in an object. You don't require threads for that.

[M4chin3]

By decoupling I meant moving the task to another thread to avoid blocking the whole program. But basically you're right, I can move the blocking tasks to threads and keep the connections all together within another thread. I'm not worrying about the number of threads shouldn't be so many, but I'm giving the limited thread pool a thought.

Thanks!

[wysota]

I'm not worrying about the number of threads shouldn't be so many

Right... and 640kB or RAM should be enough for anybody