On Wed, 20 Nov 2013 22:26:27 GMT, Jacek Furmankiewicz wrote:
P.S. I do have computationally intensive tasks happening in every request, so I know my event loop thread will block if I just code without multi-core support.
You may consider:
a) integrating computational code with fiber-even model to yield regularly and let program process stockpiled events. This will act exactly as if multi-threaded but more efficiently.
b) change the design as doing heavy computation while client is waiting sucks :) It can just timeout the connection tired of waiting. Changing client-server communication into non-blocking ones is probably a better idea, be it polls or websockets. Exact usage of threads in depends on the chosen design here. It is probably not that trivial thing to pull off if you don't have much networking programming experience.