Re: [libuv] Threaded workers which also do I/O

2016-10-20 Thread Gonzalo Diethelm
On Tuesday, October 18, 2016 at 11:52:22 PM UTC+2, Saúl Ibarra Corretgé wrote: > > > > One thing is that when I control-C out of the running server, it prints > > the following and then hangs: > > ^C[INFO] (../src/server.c:16) Received SIGINT, stopping... > > [INFO] (../src/server.c:107) Stoppi

Re: [libuv] Threaded workers which also do I/O

2016-10-18 Thread Saúl Ibarra Corretgé
If each thread is a uv loop, then you could send the connection where the request came from from one loop to another using uv_write2. That way the job of the "acceptor loop" would only be accepting and dispatching connections. That's a great suggestion. This is not how you im

Re: [libuv] Threaded workers which also do I/O

2016-10-18 Thread Gonzalo Diethelm
On Tuesday, October 18, 2016 at 7:23:54 AM UTC+2, Saúl Ibarra Corretgé wrote: > > On 17/10/16 19:41, Gonzalo Diethelm wrote: > > First post, libuv newbie. > > Hi and welcome to libuv then! > Thanks, and thank you for your thorough response. > > I am trying to understand how a multi-threaded

Re: [libuv] Threaded workers which also do I/O

2016-10-17 Thread Saúl Ibarra Corretgé
On 17/10/16 19:41, Gonzalo Diethelm wrote: First post, libuv newbie. Hi and welcome to libuv then! I am trying to understand how a multi-threaded web server would fit in the libuv design. This is how I envision it, but I have some questions. The main thread would run the HTTP accept loop, a